Skip to content
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

Closed
nfx opened this issue Feb 27, 2021 · 4 comments
Closed

Cannot go to sources of exception stack trace #200253

nfx opened this issue Feb 27, 2021 · 4 comments
Assignees
Labels
feature-request Request for new features or functionality notebook-builtin-renderers Builtin notebook output renderers for HTML, JS and images on-testplan
Milestone

Comments

@nfx
Copy link

nfx commented Feb 27, 2021

Issue Type: Bug

Screenshot 2021-02-27 at 19 15 34

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:

import pandas as pd
pd.DataFrame(42)

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
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30263608
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30244315
pythonvsdeb440:30224570
pythonvsded773:30223139
pythonvspyt875:30259475
pythonvspyt639:30264824
pythontb:30258533

@nfx
Copy link
Author

nfx commented Feb 27, 2021

Must be part of #91987

@joyceerhl
Copy link
Contributor

Thanks for the feedback @nfx. Possible dupe of microsoft/vscode-jupyter#4589

@nfx
Copy link
Author

nfx commented Feb 28, 2021

@joyceerhl this one has more details 😜

@greazer greazer added the notebook-workflow Issues that interrupt expected or desirable behavior label Aug 7, 2021
@greazer greazer added the feature-request Request for new features or functionality label May 4, 2022
@rebornix rebornix removed their assignment Dec 6, 2023
@rebornix
Copy link
Member

rebornix commented Dec 6, 2023

This can be a good feature request for the builtin error renderer.

@amunger amunger transferred this issue from microsoft/vscode-jupyter Dec 7, 2023
@amunger amunger added notebook-builtin-renderers Builtin notebook output renderers for HTML, JS and images and removed notebook-workflow Issues that interrupt expected or desirable behavior labels Dec 7, 2023
@amunger amunger added this to the Backlog milestone Dec 7, 2023
@amunger amunger closed this as completed Apr 22, 2024
@microsoft microsoft locked and limited conversation to collaborators Jun 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality notebook-builtin-renderers Builtin notebook output renderers for HTML, JS and images on-testplan
Projects
None yet
Development

No branches or pull requests

6 participants