You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Oh no! I just updated to version v2021.10.1001414422 of the Jupyter extension, and the UI changes around the kernel picker now make this issue almost impossible to work around.
Previously, the picker would show the name of each running Jupyter session in the UI, so you could tell which was likely to be the one you wanted to reconnect to (e.g. for my_notebook.ipynb you'd probably want to reconnect to an autogenerated session my_notebook-xxxx-xxxx-xxxx-xxxx for whatever value xxxxs were the autogenerated name for the session.
This was already a bit of a pain given the kernel-leaking issue above means that you typically get two or three of these for any given open notebook. But now there's just a list of anonymous sessions (see screenshot); if you have a few going in a remote server, good luck guessing which is the one you wanted if the "suggested" one isn't right.
Oh no! I just updated to version v2021.10.1001414422 of the Jupyter extension, and the UI changes around the kernel picker now make this issue almost impossible to work around.
Previously, the picker would show the name of each running Jupyter session in the UI, so you could tell which was likely to be the one you wanted to reconnect to (e.g. for
my_notebook.ipynb
you'd probably want to reconnect to an autogenerated sessionmy_notebook-xxxx-xxxx-xxxx-xxxx
for whatever value xxxxs were the autogenerated name for the session.This was already a bit of a pain given the kernel-leaking issue above means that you typically get two or three of these for any given open notebook. But now there's just a list of anonymous sessions (see screenshot); if you have a few going in a remote server, good luck guessing which is the one you wanted if the "suggested" one isn't right.
Originally posted by @zpincus in #7610 (comment)
The text was updated successfully, but these errors were encountered: