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
Hi apbailey2q, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
No built-in support yet for clickable stack traces in the Java debugger console. You can track and upvote the following open feature requests:
• support for ::
– Explains why the debugger can’t guess source locations for plain stdout messages.
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
This issue has been closed automatically because it needs more information and has not had recent activity. Please reach out if you have or find the answers we need so that we can investigate further.
Activity
github-actions commentedon Apr 16, 2026
Hi apbailey2q, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
No built-in support yet for clickable stack traces in the Java debugger console. You can track and upvote the following open feature requests:
• clickable stack trace in java debugger output
– Parse exception text and make each “at …(.java:line)” clickable.
• Include stacktrace info when stopping at exception breakpoint
– Print full stack trace in the editor/console when pausing on exceptions.
Other references with low confidence
• support for ::
– Explains why the debugger can’t guess source locations for plain stdout messages.
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
github-actions commentedon May 1, 2026
This issue has been closed automatically because it needs more information and has not had recent activity. Please reach out if you have or find the answers we need so that we can investigate further.