Choose kernel and reconnect to running kernel#7191
Conversation
…d nasty jupyter session behavior
… IJupyterKernelSpec instead of storing just the uuid in the settings.
…URI each time. This seems to have messed up the ability to connect to the same server and start a new kernel.
|
|
|
Hi @rchiodo, Any news on this? I'm willing to put in extra work to make this happen quicker. Thanks |
|
Wasn't sure if you were continuing to work on this or not? Unfortunately we aren't going to take it up anytime soon as we're all heads down on supporting notebooks at the moment. In order to submit this you might have to refactor some stuff as we've changed quite a bit for notebook support. If you want to try updating, we're happy to review it again. I think we were all okay with the extra setting for picking the remote kernel. |
|
Great. |
|
It was easier to re-implement than play around with trying to merge the changes. |
For #7014 , #3763
Fixes the requested changes on #7015 and adds the ability the select the remote kernel to connect to. This was done together since the kernel uuid is passed down using IJupyterKernelSpec instead of setting a different setting just for the kernel UUID.
Test plan is updated as appropriatepackage-lock.jsonhas been regenerated by runningnpm install(if dependencies have changed)