Kernel selector should be auto displayed after specifying local or remote Jupyter server for connections #8795
Labels
feature-request
Request for new features or functionality
notebook-kernel
Kernels issues (start/restart/switch/execution, install ipykernel)
notebook-remote
Applies to remote Jupyter Servers
verification-needed
Verification of issue is requested
verified
Verification succeeded
Milestone
Testing #8778
I found the flow to add a remote kernel somewhat unintuitive. The user has to do the following:
After step 1 I was surprised that no kernel was autoselected and my previous, local kernel connection remained the same, and I needed to go into a different UI entrypoint to select the kernel. I suppose we can't autoselect a kernel from the remote connection because there could be multiple kernels running on the remote server? If that's the case, could we nudge users to pick the kernel by immediately invoking
notebook.selectKernel
with no arguments to put up the kernel selector?The text was updated successfully, but these errors were encountered: