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
Note: This might also be moved to my plate if we want to do something here.
Right now the kernels come in in chunks. But there is no indication of when more are added aside from popping the kernel picker. I notice it more in testing, but also in usage. Basically some time X after loading I'll have my selections available, but I never know the exact time, and have to pop open the kernel picker several times to see when they are loaded. Applies to both the type of kernels being loaded or detecting a new one.
The text was updated successfully, but these errors were encountered:
Reported internally I have been using the pre-release Jupyter and Python extensions, and I still see some odd behavior with kernel picking. Specifically, after a window reload the extension seems to pick an arbitrary kernel and no conda-based kernels are displayed. Then after 5-10 seconds it discovers the conda environments and then selects the kernel correctly.
Testing #11755
Note: This might also be moved to my plate if we want to do something here.
Right now the kernels come in in chunks. But there is no indication of when more are added aside from popping the kernel picker. I notice it more in testing, but also in usage. Basically some time X after loading I'll have my selections available, but I never know the exact time, and have to pop open the kernel picker several times to see when they are loaded. Applies to both the type of kernels being loaded or detecting a new one.
The text was updated successfully, but these errors were encountered: