-
Notifications
You must be signed in to change notification settings - Fork 32.5k
Asynchronously verified breakpoints are not always marked as "verified" within the UI #86749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@connor4312 this should not happen. Our approach is to show the breakpoint as verified if at least one session verified it. How does the child session verify the breakpoint, does it send a breakpoint |
@isidorn it looks like those source references don't exist any more, could you update them? The child session does send a changed event. If you try to reproduce it, note that in the most recent version of PWA we made a change to work around this issue--we try to resolve the BP in the initial setBreakpoints response--you'll want to check out cd910d020466b089f920ea50c8ba0f6168bab278 and run |
@connor4312 Sorry this somehow slipped through my radar.
The data object is session specific data for a breakpoint. Point is we should figure out why the breakpoint thinks it is not verified and from what session does it read the data. |
@connor4312 do you have some nice steps to reproduce this without having a container? Is it possible to reproduce this locally? Did the code pointers I provided help? |
@connor4312 friendly ping for my previous question. |
Apologies, will check this out tomorrow morning! |
No problem and no hurries. Thanks |
I actually cannot reproduce this on the latest insiders, though I can on an old 1.41 install I had lying around on a VM. Maybe the ordering PR fixed this? Closing unless we see it happening again. |
Ok, thanks for looking into this! |
Observed by @testforstephen in #83743 (comment) and myself in microsoft/vscode-js-debug#144 -- the latter has steps to reproduce the issue.
The text was updated successfully, but these errors were encountered: