You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
connor4312 opened this issue
Mar 27, 2020
· 3 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
See microsoft/vscode-js-debug#390 (comment): You should be able to reproduce by following the verification instructions with a js-debug-nightly version <= 2020.3.2517
The text was updated successfully, but these errors were encountered:
connor4312
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Mar 27, 2020
Double check the parent session after returning from initialize (maybe launchAndAttach to?). Iff it's present and in State.Inactive, then terminate it and reject the request with a 'canceled' error
For the specific problem, it's probably safe to ignoreErrors in .expand. I see we do this elsewhere in the file. The set is cleared after that function runs, so ignoring problems here shouldn't have negative effects on state elsewhere.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
See microsoft/vscode-js-debug#390 (comment): You should be able to reproduce by following the verification instructions with a js-debug-nightly version <= 2020.3.2517
The text was updated successfully, but these errors were encountered: