vscode-powershell icon indicating copy to clipboard operation
vscode-powershell copied to clipboard

Adding invalid string-interpolated watch expression puts watch window in bad state

Open NeoXtreem opened this issue 3 years ago • 2 comments

Prerequisites

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

Summary

Adding an invalid string-interpolated watch expression as a third watch expression puts the watch window in bad state and makes it unusable.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.2.1
PSEdition                      Core
GitCommitId                    7.2.1
OS                             Microsoft Windows 10.0.22000
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

1.64.0
5554b12acf27056905806867f251c859323ff7e9
x64

Extension Version

[email protected]

Steps to Reproduce

  1. Debug PowerShell script and hit a breakpoint.
  2. Add expression a to watch window.
  3. Add expression a to watch window again.
  4. Add expression "a${a[a]}" to watch window.

The entry for the last watch expression added shows :. If double-clicked, it shows "a${a[a]}":. However, at this point, it is impossible to change, add or remove watch expressions without killing the PowerShell terminal.

Visuals

No response

Logs

No response

NeoXtreem avatar Feb 06 '22 20:02 NeoXtreem

Thanks for opening this issue @NeoXtreem! Is this currently breaking any workflows for you?

StevenBucher98 avatar Feb 09 '22 23:02 StevenBucher98

@StevenBucher98 No, but it does require me to restart Visual Studio whenever it happens.

NeoXtreem avatar Feb 24 '22 23:02 NeoXtreem

I can't seem to repro this in v2023.8.0.

andyleejordan avatar Nov 18 '23 01:11 andyleejordan

This issue has been labeled as resolved and has not had any activity for one or more days. It has been closed for housekeeping purposes.

github-actions[bot] avatar Nov 19 '23 01:11 github-actions[bot]