-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
Notebook controller always defaulting to Pyolite with the new MRU kernel picker #171385
Comments
after updating I'm no longer hitting this |
My scenario:
I've seen this happen a lot in the past day and today |
First output
Second reload (kernel is not auto selected)
|
This bug has been fixed in the latest release of VS Code Insiders! @DonJayamanne, you can help us out by commenting If things still don't seem right, please ensure you're on version 07d6f5b of Insiders (today's or later - you can use Happy Coding! |
Still running into this.
Here is the
Yes the controllers have been created and regsietered here are the jupyter logs confirming the fact that the controllers are registered
|
|
@DonJayamanne and I debugged together, and here are our findings. Basically it's a race condition but it should be prevented.
In @DonJayamanne 's case, he has 90+ kernels, registering them takes long time. When reloading the window, the editor tries to restore the kernel, but can't find a matching kernel, thus it skips restoring the selected kernel. I guess removing selected kernel from notebook binding for all notebooks is not expected from the commit title "Keep selected kernel from untitled notebook when saving". |
I hardly remember this change at all but I'll take a look! |
I think the change you're referring to is for
Basically, remove the notebook binding for the untitled document when it's closed when saving and switching to the new saved notebook. I think this should be ok, it's treating the notebookBindings list as active notebook bindings.
I'm actually not seeing that- I see that when I close a notebook, first the NotebookEditorWidget gets its editor view state which includes the selected kernel id, then second, we close the notebook textmodel and fire the event that it was closed, and the kernel service removes the kernel from
This is an issue and I can repro it with my kernels if I do this
I suggest letting the view state restore set the previous kernel id into Looking over the code, I'm not sure whether it will be an issue somewhere for |
…lose And also only persist the selected kernel in the editor view state for untitled notebook editors Fix #171385
…lose (microsoft#173352) And also only persist the selected kernel in the editor view state for untitled notebook editors Fix microsoft#171385
@DonJayamanne can you verify this? |
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
helo_world1234.ipynb
pyolite
Expected experience - as a user I would be required to select a kernel
The text was updated successfully, but these errors were encountered: