-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Cannot go to sources of exception stack trace #200253
Labels
Milestone
Comments
Must be part of #91987 |
Thanks for the feedback @nfx. Possible dupe of microsoft/vscode-jupyter#4589 |
@joyceerhl this one has more details 😜 |
greazer
added
the
notebook-workflow
Issues that interrupt expected or desirable behavior
label
Aug 7, 2021
This can be a good feature request for the builtin error renderer. |
amunger
added
notebook-builtin-renderers
and removed
notebook-workflow
Issues that interrupt expected or desirable behavior
labels
Dec 7, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Type: Bug
Let's imagine some hypothetical bad code that resulted in exception either because bad or unfamiliar third-party libraries and focus on speed of issue resolution:
Upon executing this, we get an exception. As professional IDE user, I expect a consistent behavior and exception stack trace rendered like a normal stack trace - something compact, with clickable lines, that get me to correct lines of code, causing the error. I do not want to open search bar in the project, then figure out that this is not the error in the project i'm working on, but rather in third-party dependency, because that way i have to go, figure out where the sources of that dependency are, open another editor, find references, etc etc. I also really don't want to see the same exception message for 3 times. Practically speaking, we can make hiding of stack traces as opt-out feature. If make with bottom-right notifications popup - even better :)
VSCode has a nice stack trace rendering widget in debug mode, so that one could be just re-used in this beautiful extension, so that I'd see consistent UX across different parts of the editor for the same type of things.
...
Extension version: 2021.3.600686576
VS Code version: Code - Insiders 1.54.0-insider (Universal) (e590188, 2021-02-26T20:39:12.763Z)
OS version: Darwin x64 19.6.0
A/B Experiments
The text was updated successfully, but these errors were encountered: