-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Active inline breakpoint isn't highlighted #81718
Labels
debug
Debug viewlet, configurations, breakpoints, adapter issues
feature-request
Request for new features or functionality
verification-needed
Verification of issue is requested
verified
Verification succeeded
Milestone
Comments
isidorn
added
debug
Debug viewlet, configurations, breakpoints, adapter issues
feature-request
Request for new features or functionality
labels
Oct 1, 2019
Good catch. We currently do not support this. |
connor4312
added a commit
that referenced
this issue
Nov 1, 2019
…correctly In #81718 we adjusted breakpoint display logic to show an 'empty' arrow on the line, and the arrow with a dot at the column where the debugger is running. However, not all debuggers support column breakpoints. Bowden noticed, while working on his Python demo for ignite, that breakpoints in Python code no longer displayed correctly. This PR tweaks the logic so that if we see a breakpoint that doesn't have an associated column, we show the arrow with a dot on the line, rather than assuming that there'll be an inline indicator arrow.
I found an issue with this change and opened a PR for it: #83851 |
connor4312
added a commit
that referenced
this issue
Nov 1, 2019
…correctly In #81718 we adjusted breakpoint display logic to show an 'empty' arrow on the line, and the arrow with a dot at the column where the debugger is running. However, not all debuggers support column breakpoints. Bowden noticed, while working on his Python demo for ignite, that breakpoints in Python code no longer displayed correctly. This PR tweaks the logic so that if we see a breakpoint that doesn't have an associated column, we show the arrow with a dot on the line, rather than assuming that there'll be an inline indicator arrow.
connor4312
added a commit
that referenced
this issue
Nov 1, 2019
…correctly In #81718 we adjusted breakpoint display logic to show an 'empty' arrow on the line, and the arrow with a dot at the column where the debugger is running. However, not all debuggers support column breakpoints. Bowden noticed, while working on his Python demo for ignite, that breakpoints in Python code no longer displayed correctly. This PR tweaks the logic so that if we see a breakpoint that doesn't have an associated column, we show the arrow with a dot on the line, rather than assuming that there'll be an inline indicator arrow.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
debug
Debug viewlet, configurations, breakpoints, adapter issues
feature-request
Request for new features or functionality
verification-needed
Verification of issue is requested
verified
Verification succeeded
re #81175
The text was updated successfully, but these errors were encountered: