Vscode-powershell: Can't edit watch variables when paused in debugging

[JustinGrote]

Issue Description

When paused in the debugger:

This works fine with the stable extension, probably something to do with the backend rewrite.

Attached Logs

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

Environment Information

Visual Studio Code

| Name | Version |
| --- | --- |
| Operating System | Windows_NT x64 10.0.19041 |
| VSCode | 1.42.0-insider|
| PowerShell Extension Version | 2019.12.1 |

PowerShell Information

|Name|Value|
|---|---|
|PSVersion|5.1.19041.1|
|PSEdition|Desktop|
|PSCompatibleVersions|1.0 2.0 3.0 4.0 5.0 5.1.19041.1|
|BuildVersion|10.0.19041.1|
|CLRVersion|4.0.30319.42000|
|WSManStackVersion|3.0|
|PSRemotingProtocolVersion|2.3|
|SerializationVersion|1.1.0.1|

Visual Studio Code Extensions

Visual Studio Code Extensions(Click to Expand)

|Extension|Author|Version|
|---|---|---|
|azure-account|ms-vscode|0.8.7|
|azure-pipelines|ms-azure-devops|1.157.4|
|better-align|wwm|1.1.6|
|better-comments|aaron-bond|2.0.5|
|better-powershell-syntax-highlighting|justin-grote|0.0.2|
|bracket-pair-colorizer-2|CoenraadS|0.0.29|
|code-settings-sync|Shan|3.4.3|
|gc-excelviewer|GrapeCity|2.1.32|
|gistfs|vsls-contrib|0.0.38|
|git-graph|mhutchie|1.20.0|
|gitlens|eamodio|10.2.0|
|indent-rainbow|oderwat|7.4.0|
|markdown-all-in-one|yzhang|2.6.1|
|powershell-preview|ms-vscode|2019.12.1-CI.41180|
|remote-containers|ms-vscode-remote|0.96.0|
|remote-ssh-edit-nightly|ms-vscode-remote|2019.12.34080|
|remote-ssh-nightly|ms-vscode-remote|2019.12.34080|
|remote-wsl|ms-vscode-remote|0.42.0|
|team|ms-vsts|1.161.0|
|todo-tree|Gruntfuggly|0.0.162|
|vscode-icons|vscode-icons-team|9.7.0|
|vscode-peacock|johnpapa|3.2.0|
|vscode-sort-json|richie5um2|1.18.0|
|vscode-zipexplorer|slevesque|0.3.1|

[SeeminglyScience]

@JustinGrote If you change them, then press enter in the integrated console, do they update?

[SydneyhSmith]

@JustinGrote thanks for reporting this...I am having a bit of trouble reproducing this...are you using a Debug configuration?

[JustinGrote]

I've noticed it happens after extended debugging sometimes but not right
away. Let me see if I can get a better capture with detailed PSES logs.

On Mon, Jan 6, 2020, 2:24 PM Sydney Smith [e-mail] wrote:

@JustinGrote https://github.com/JustinGrote thanks for reporting
this...I am having a bit of trouble reproducing this...are you using a
Debug configuration?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PowerShell/vscode-powershell/issues/2396?email_source=notifications&email_token=ADUNKUUYJQQIS4WEPHBNKX3Q4OHQFA5CNFSM4KBXFQ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIGVNNA#issuecomment-571299508,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADUNKURL4HIF5PDDVCNWVSTQ4OHQFANCNFSM4KBXFQ6Q
.

[msftbot[bot]]

This issue is being closed as inactive, if this issue is still occurring it will be re-opened

[rjmholt]

I wonder if this is related to https://github.com/PowerShell/vscode-powershell/issues/2364

[JustinGrote]

@rjmholt @TylerLeonhardt Just confirming this is definitely still an active issue, I'll see it after doing complicated debugging, start/stopping debug etc. after 3-5 minutes or so, however I haven't been able to nail down a root cause.

I'll turn on Debug logging and see if I can catch it in the act and submit the logs.

[rjmholt]

Sorry, this was closed by accident in the PR I just merged. It may be fixed by that, but needs to be manually tested.

[JustinGrote]

@rjmholt thanks! I'll grab a CI build VSIX and give it a shot, this has been happening a lot to me during long interactive sessions.

[JustinGrote]

Just an update that this still happens to me all the time and I haven't been able to take the time to capture a full output or make it consistently reproducible, but it happens on 2020.3.2

It generally happens when I have this type of workflow:

1. Set a breakpoint
2. Start Powershell Interactive Session
3. Run a script or command and hit said breakpoint
4. Stop the debug rather than continue (I think the problem is in some cleanup somewhere here)
5. Start Interactive Session Again
6. Hit breakpoint but now I can't edit or change the watch variables, and they don't update