debugger won't focus on files that are not under the current file's directory in vscode 1.31

[AndyP2]

Unexpected behaviour in vscode 1.31:

• start debug session on a .ps1 file
• step into a .ps1 file on a path that is not below the current file, i.e. whose relative path has .. in it
• observe that focus stays on the original file, even though execution has now paused in the called file
• observe that switching focus to the called file and single stepping switches back to the original file

Downgrade back to vscode 1.30.2 to see desired behaviour:

• start debug session on a ps1 file
• step into the same script file
• observe the focus switches to the called file
• observe that single stepping keeps focus on the called file

What changed between 1.30.2 and 1.31? Is this just a powershell issue or does it occur in other languages? It looks like it's trying to implement 'just my code' but I can find no way to turn it off except to stay on 1.30.2.

[corbob]

I started seeing this near the end of January, but couldn't describe it this well. I suspect as there were no changes to the extension at the time it started to occur to me that it's a vscode issue, but I have no idea where to start looking.

Another thing I noticed is that the debug sidebar doesn't list any variables while it's not in the current file.

[mrboring]

I'm having the same issue with VS Code 1.31. When I debug a Pester test, and step through the code into a function defined in a different file, the focus stays in the Pester file. When I switch back to VS Code 1.30.2, the step through works fine and VS Code switches into the file holding the function.

I get the same behaviour with the PowerShell extension versions: 1.11.0 and 2..0.0 preview.

[corbob]

Part of me is wondering if this is related to vscode bug: microsoft/vscode#67895 unfortuantely I don't know enough about the inner workings of the debugger in vscode to know if they're related ☹️

[exactmike]

having this problem as well. exactly as described.

[rjmholt]

If the same version of the PowerShell extension does or doesn't have this across different VSCode versions, it's likely this is a VSCode issue.

We'll need to work out if it's something they intended to break or not.

[SydneyhSmith]

Thanks guys, we are able to repro this. We will need to investigate further what changed in the release to have caused this.

[weinand]

@SydneyhSmith please see issue microsoft/vscode#68616 that might be related (and my comment microsoft/vscode#68616 (comment)).

Do you set the "deemphasized" hint on the top stack frames?
If yes, do you have an option to turn "deemphasizing top frames" off?
This helped for Node.js debug.