-
Notifications
You must be signed in to change notification settings - Fork 504
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
Report errors when notebook execution fails #34
Comments
Having a way to inform the user when the kernel is restarted would also be useful (out of memory for example which can happen after the notebook has been executed). |
If you have a notebook with code: raise Exception("hi"); When serving it, you get a 503 and the following in the logs:
Would be nice to show this to the user, however we have to consider the security implications of showing unfiltered exception info to users. It might leak data that shouldn't be leaked. |
Solved in #186 |
Currently, this merely results in a 503 error screen.
More details could be made available to the user (optionally since, this could give information about the code being executed).
The text was updated successfully, but these errors were encountered: