PowerShell / PowerShell/vscode-powershell
Breakpoints not cleaned up if Debug Interactive Session is stopped.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Issue Description
If the Interactive Debugger is started, then a breakpoint is set, but then the Interactive Debugger is then stopped, the breakpoints are still present and are not synced with the breakpoint activity bar. Further runs will still trigger debug mode even if the system currently isn't in the interactive debugger.
If PSBreakpoints are cleared when the debugger stops, this should fix it. This may be a PSES issue.
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.0 |
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 |
|---|---|---|
| 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.21 |
| git-graph | mhutchie | 1.19.1 |
| 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.0 |
| remote-containers | ms-vscode-remote | 0.95.0 |
| remote-ssh-edit-nightly | ms-vscode-remote | 2019.12.24000 |
| remote-ssh-nightly | ms-vscode-remote | 2019.12.24000 |
| remote-wsl | ms-vscode-remote | 0.41.6 |
| todo-tree | Gruntfuggly | 0.0.162 |
| vscode-icons | vscode-icons-team | 9.6.0 |
| vscode-peacock | johnpapa | 3.2.0 |
| vscode-sort-json | richie5um2 | 1.18.0 |
| vscode-zipexplorer | slevesque | 0.3.1 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the sequence in the VS Code PowerShell extension: start an Interactive Debugger, set a breakpoint, stop the session, and run again. Trace the debugger-stop handling and PSBreakpoints synchronization; done means stopped sessions clear their breakpoints, update the activity bar, and no longer trigger interactive debug mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100