Closed jgriss closed 6 years ago
I am able to reproduce this issue with a simple notebook that only contains a cell displaying out "execute next cell" button. Depending on when you close the notebook, cells get re-executed when reopening the notebook.
Current ideas:
This issue should be fixed with the new button (bd8cd9ff3bd530cf8999e37c9067d7ed2b88ece4)
When re-opening the workbook of the spiked dataset, the Python Kernel started at 100% load and took very long.
This might be caused by the way we "inject" our code into the Notebook. It could, for example, be, that the injected JavaScript code that we use to execute subsequent cells is re-executed when loading the notebook.