Skip to content

Asynchronously verified breakpoints are not always marked as "verified" within the UI #86749

Closed
@connor4312

Description

@connor4312

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:

  1. The 'stubbed' parent debug session gets a setBreakpoints request. It returns unverified BP (and never verifies them).
  2. The child debug session gets a setBreakpoints request. It also initially returns the BPs as unverified,
  3. 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.

Metadata

Metadata

Assignees

Labels

*not-reproducibleIssue cannot be reproduced by VS Code Team member as describedbugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions