-
Notifications
You must be signed in to change notification settings - Fork 34.1k
Closed
Labels
*not-reproducibleIssue cannot be reproduced by VS Code Team member as describedIssue cannot be reproduced by VS Code Team member as describedbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeededVerification succeeded
Milestone
Description
Observed by @testforstephen in #83743 (comment) and myself in microsoft/vscode-js-debug#144 -- the latter has steps to reproduce the issue.
What I'm seeing is that:
- The 'stubbed' parent debug session gets a setBreakpoints request. It returns unverified BP (and never verifies them).
- The child debug session gets a setBreakpoints request. It also initially returns the BPs as unverified,
- then a few milliseconds later (once we get confirmation from CDP) the child verifies them.
I think the correct behavior is for the BP to show as verified if any debug session verifies them, and this usually works. So I suspect there's some timing issue in vs code itself here.
testforstephen
Metadata
Metadata
Assignees
Labels
*not-reproducibleIssue cannot be reproduced by VS Code Team member as describedIssue cannot be reproduced by VS Code Team member as describedbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeededVerification succeeded