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

Changing Kernel By Selecting Kernel Name does not handle errors #7093

Closed
IMAM9AIS opened this issue Aug 26, 2019 · 1 comment
Closed

Changing Kernel By Selecting Kernel Name does not handle errors #7093

IMAM9AIS opened this issue Aug 26, 2019 · 1 comment
Labels
status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.

Comments

@IMAM9AIS
Copy link

Jupyter lab has the functionality of changing kernels by clicking on kernel name on top right hand side of the file.

Two scenarios arise when this is clicked:-

  1. Kernel change happens without any errors which is fine.

  2. There is some exception that gets generated in which case, the kernel silently switches back to the original kernel, without any exception message being thrown on the screen. Although we have exceptions being printed in the lab server, this is not user friendly. We identified this issue while using remote kernels being spawned through Jupyter enterprise gateway, where we limit the number of kernels being launched. Once the user reaches the required amount of kernels, the user is not able to switch the kernel also, without any exception being seen on screen.

@IMAM9AIS
Copy link
Author

Closing issue resolved by #7094

@lock lock bot added the status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Sep 26, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Sep 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

No branches or pull requests

1 participant