Handled case with inline disabled breakpoint gets reactivated#155403
Merged
roblourens merged 2 commits intomicrosoft:mainfrom Sep 7, 2022
Merged
Conversation
Member
|
Thanks for the PR. I am heading out of town and will review for our next release. |
roblourens
approved these changes
Sep 2, 2022
roblourens
approved these changes
Sep 3, 2022
bpasero
approved these changes
Sep 5, 2022
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR fixes #154998.
I think these are the lines where it fails.
vscode/src/vs/workbench/contrib/debug/browser/breakpointEditorContribution.ts
Lines 682 to 688 in 7839742
Looks like we have three cases here when we click on an
InlineBreakpointWidget, but right now we handle only two.If
this.breakpointisundefined, a new breakpoint is added.If
this.breakpointis defined, the current implementation callsaddBreakpointswhich apparently fails because the breakpoint already exists, it's just disabled.By explicitly handling when
this.breakpointis defined but disabled, as shown in this PR, looks like the issue is gone.