Cannot inspect variables or use debug commands in Azure Functions in terminal

[yobyot]

Issue Description

Debugging an Azure Function using the PowerShell extension for VS Code.

Attached Logs

Follow the instructions in the README about
capturing and sending logs.

Environment Information

Visual Studio Code

Name	Version
Operating System	Darwin x64 20.2.0
VSCode	1.52.1
PowerShell Extension Version	2020.6.0

PowerShell Information

Name	Value
PSVersion	7.1.1
PSEdition	Core
GitCommitId	7.1.1
OS	Darwin 20.2.0 Darwin Kernel Version 20.2.0: Wed Dec 2 20:39:59 PST 2020, root:xnu-7195.60.75~1/RELEASE_X86_64
Platform	Unix
PSCompatibleVersions	1.0 2.0 3.0 4.0 5.0 5.1.10032.0 6.0.0 6.1.0 6.2.0 7.0.0 7.1.1
PSRemotingProtocolVersion	2.3
SerializationVersion	1.1.0.1
WSManStackVersion	3.0

Visual Studio Code Extensions

Visual Studio Code Extensions(Click to Expand)

Extension	Author	Version
aws-toolkit-vscode	amazonwebservices	1.18.0
azure-account	ms-vscode	0.9.4
azurerm-vscode-tools	msazurermtools	0.14.0
gitlens	eamodio	11.1.3
powershell	ms-vscode	2020.6.0
vscode-azurefunctions	ms-azuretools	1.1.0
vscode-dotnet-runtime	ms-dotnettools	1.0.0
vscode-icons	vscode-icons-team	11.1.0
vscode-logicapps	ms-azuretools	1.0.2

Problem description

I hope the two attached animations make the point: I cannot debug an Azure Function in VS Code. As you can see, it's possible to do so in pwsh consoles. If there's a setting that enables a regular debugging session in VS Code, I can't find it so I am reporting this as a bug. I hope it's a user error (caused by pitiful doc) and not one of those "You just can't do it in VS Code" issues that seem to plague the PowerShell environment in VS Code.

Debugging in a pair of consoles (works):

Debugging in VS Code (no input possible):

[SydneyhSmith]

Thanks @yobyot it would be really helpful if you could also attach the logs--instructions for how to do that are here ! Thanks for providing the GIFs and description those are great!

[yobyot]

@SydneyhSmith

Hi. I've sent a .zip of the requested logs to vscode-powershell@microsoft.com.

[yobyot]

FWIW, here's a screenshot from a virgin Windows 10 machine, running pwsh 7.1.1, latest pwsh extension and Core Tools running the default Azure Functions HTTP project with a breakpoint set. This VM is in a client environment completely separate from the macOS environment from which I first reported this problem.

It's been, literally, years and years now that the PowerShell extension hasn't played nice with the VS Code debugger. I've reporting only a few of the issues I've experienced, all of which either were closed with pointed fingers elsewhere or were "wait for us to rearchitect." It makes one long for the ISE -- however limited it was, it was reliable. I just don't understand how PowerShell developers can be expected to depend on this extension, which is still labelled "preview" (and not to be confused with the "preview, preview" version of the extension).

If I'm doing something wrong, I'd be happy to fix it -- providing it's documented. As it is, the paragraph or two on debugging a function in VS Code is embarrassingly thin.

[SydneyhSmith]

Thanks @yobyot for all the detailed information, we really appreciate it. Unfortunately, this will take more investigation on our part--thanks for your patience!

[yobyot]

Hello, pwshTeam.

Any update on this issue? A workaround? Anything?

It's so hard to write an Az Function using the command line debugger.

Thanks.

[andyleejordan]

Can you confirm it's not working in the same manner with the latest release? We switched to use the Debug Adapter Protocol in February. On that note, the debugger is actually getting rewired (again, but it's necessary) as part of PowerShell/PowerShellEditorServices#1295