-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
Empty raw cell & lost code cells in the virtual notebook #10435
Comments
I originally noticed it in an existing long notebook at the very end of it (so my reproduction attempts focused on it), but in that case it was not related to running cells at all - it was in there since the notebook was opened. |
@krassowski I have tried a notebook with many empty cells (like your example) with current master, and indeed, I see a un-rendered cell at the end when I scroll. This happens in the case [1] I wait to scroll so the rendering is complete, and then scroll down to the bottom [2] If I scroll down while the virtual rendering is still happening. Is this the issue you were reporting or do you see also other issue (you are talking about "eat code cell")? The remaining unrendered cell issue does not show-up with jupyterlab 2.3. Master aims to contain a port of the logic present in 2.3, so this maybe something to look at to nail-down the issue. |
Yes this is the same issue, and yes there is (sometimes, not every time) an extra issue of executed cell disappearing; please see the GIF in first comment it was caught on record there; it does not happen every time I could not narrow conditions down.
Yes, #10428 is another issue where it worked in 2.3 but does not work in 3.1. |
The reproduction for the lost cell is in #10488. |
Fixed with #10505 |
Description
An empty un-rendered raw cell appears in the virtual notebook on some undetermined actions. It can also eat the code cells as on the gif below.
Reproduce
This one is extremely difficult to reproduce. There is some chaos factor and it only appears one in a dozen attempts. Async isuse/race condition?
Context
The text was updated successfully, but these errors were encountered: