Debugging is broken in v2022.9.0

[kborowinski]

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

After upgrading extension to latest preview version v2022.9.0 I can't start interactive debugging or attach to existing PowerShell session.

Downgrading extension to v2022.8.5 solves the problem.

launch.json:

{
    "name": "PowerShell: Interactive Session",
    "type": "PowerShell",
    "request": "launch"
},
{
    "name": "PowerShell Attach to Host Process",
    "type": "PowerShell",
    "request": "attach",
    "runspaceId": 1
},
{
    "name": "PowerShell Attach Interactive Session Runspace",
    "type": "PowerShell",
    "request": "attach",
    "processId": "current"
}

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.2.6
PSEdition                      Core
GitCommitId                    7.2.6
OS                             Microsoft Windows 10.0.19044
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0, 5.0, 5.1.10032.0, 6.0.0, 6.1.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

1.72.0-insider
835d39cfac9ede6c7c90678c8d6c3d4d0171ed6d
x64

Extension Version

[email protected]
[email protected]

Steps to Reproduce

1. Upgrade extension to latest preview version v2022.9.0.
2. Start debugging interactive session or attach to existing PowerShell session

Visuals

Interactive debugging:

Attaching to existing session:

Logs

20220928T120302.zip

[kborowinski]

Is it related to this PR? I do not set cwd in the launch.json. Setting it to empty "cwd": "" does not help either.

[andyleejordan]

Good find! I'll ping you on Discord to test something for me.