-
Notifications
You must be signed in to change notification settings - Fork 5k
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
sequential queueing of cells not working #6898
Comments
update: if i use "Run All Below" instead of hitting shift-enter a bunch, the queueing works fine.. |
@leoscholl Thanks for your contribution! Which browser are you using? Does the bug still occur if you try a different browser or the same browser in private/etc mode, without extensions? Also, have you tried using the Notebook 7 beta? Does this error recur in the newer version? |
I’m using the latest chrome on windows, it’s version 114.0.5735.110 Have not tried notebook 7 beta. Is it possible to install side by side with 6? |
You can install it side-by-side with NBClassic (which provides the classic notebook 6 UI): https://jupyter-notebook.readthedocs.io/en/latest/migrating/multiple-interfaces.html |
Hi @leoscholl, please try this out in Notebook 7. This might not be something that we can fix in Notebook 6 at the moment. |
@RRosio, I am facing the same issue currently with the following version of core packages
@leoscholl , Was this issue resolved for you with notebook 7? |
@RRosio, Could you help with this issue. It is still occurring with notebook 7 as well. |
I am using jupyterlab now with no issues. Have not tried notebook 7. |
@leoscholl , Can you share versions of your core packages? |
@leoscholl, If possible can you share versions of your core packages? |
Hi @divyabiyani this is what I have installed:
Notebook 6 not working correctly but jupyterlab 3.6.5 works fine. |
Still facing this issue:
No browser I've tried works. Shift+Enter to execute cells only runs the first cell and skips the rest if the first cell execution does not complete instantly. |
After playing around with this a bit more, I found that disabling the "Variable Inspector" nbextension solved my issues. I see from your screenshot that you have it enabled @leoscholl. Hopefully that fixes it for you as well, albeit 6 months late :) |
Thank you @danielqu22. @leoscholl, if this issue is still relevant, could you please check if you have "Variable Inspector" nbextension installed ( |
@andrii-i I have had this issue too (for some months). I can confirm that disabling 'Variable Inspector' fixes the issue for me thanks @danielqu22 |
thanks @danielqu22 for figuring this out. Yes, disabling variable inspector fixes the issue for me too. |
Hey @danielqu22. Thanks for the suggestion. Post this fix, I am facing another issue wherein the sequential cells stop working if the current cell execution time is more than 8-10 minutes. Upon further investigation, it turns out that the kernel's execution_state becomes idle post this long time taking cell's execution. It might be because of last_Activity not getting updated in this post 8-9 minutes. Is there a way to increase the kernel_idle_timeout? cc: @leoscholl |
I'm having issues similar to #5098 #4825 and #6794 which are all unresolved.
When i first run cells in a new notebook, new environment with just python3.9 and ipykernel, things work fine.
But if I try to queue up some more cells, only the first one runs.
Notice the "executed in 0ms" messages after trying to run those cells.
In the jupyter console I get these "Kernel does not exist" messages, not sure if it is related or not:
This wasn't a problem until about a month ago when it started happening all the time. Don't know what changed. Tried updating notebook and ipykernel but neither made a difference.
The text was updated successfully, but these errors were encountered: