-
Notifications
You must be signed in to change notification settings - Fork 66
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
Kernel execution errors not being rendered in OutputArea #759
Comments
Hi team, sorry to nudge here. If anyone has an idea of where I could start looking I would be happy to attempt a pull request thanks! |
This seems like a regression as previously we have always rendered errors, will take a look @sglyon |
@sglyon fix in place, will go out on next release, hopefully tomorrow |
Amazing. Thank you @stevejpurves I will test this out and hope for the best ;) |
Thank you @stevejpurves I just updated based on a build from |
Hello! I'm using thebe in a project and have run into a snag.
Kernel outputs are shown nicely (including widgets and multimedia) when code succeeds, however when there is a runtime error in the kernel nothing is shown.
I recorded a video clip walking through the error: https://app.screencastify.com/v3/watch/492g6QRsO1NjMOjdrg13
You can also reproduce by
assert False
)What you will see is no rendered output in the
OutputArea
, but you will see the traceback printed to the javascript consoleWhat we want to see is the errors rendered in the
OutputArea
.The text was updated successfully, but these errors were encountered: