This repository was archived by the owner on Oct 2, 2021. It is now read-only.
Ignore bp resolved for unknown script #325
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6abfb88 to
b567846
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Edge reports the breakpointResolved event even when the setBreakpointByUrl call can resolve the breakpoint immediately. That results on onBreakpointResolved being called with a breakpointId it doesn't recognize, and sending an incorrect event to VS Code which makes the breakpoints stop working properly.
Until the extra breakpointResolved gets fixed on Edge, this workaround will prevent us from emitting the event without a valid breakpointId to the client.