-
Notifications
You must be signed in to change notification settings - Fork 273
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
When no kernel is found, jupter-run crashes with a traceback #993
Comments
Looks like this is the intended behavior, but NoSuchKernel is no longer raised at KernelManager instantiation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
in Fedora, we use Automatic Bug Reporting Tool https://github.com/abrt/abrt
When a packaged software "crashes", the tool records that and encourages users to report it as a bug.
It also detects Python software that ends with a Traceback.
We have encountered an user report that running
/usr/bin/jupyter-run
with no kernel installed results in a Traceback and it is reported as a crash.I tried reproducing this with pip-installed jupyter-client.
When I create a Python virtual environment on my machine and install jupyter-client in it, I cannot reproduce, because (presumably) it finds my kernels in /usr/share/jupyter/kernels/ and/or ~/.local/share/jupyter/kernels/.
However, if I use an empty podman container, I can reproduce:
Would it be possible to not show the traceback in this case and simply end the app when
[RunApp] ERROR | No such kernel named python3
is displayed, with a non-zero exit code?The text was updated successfully, but these errors were encountered: