-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Data loss as notebook does not get saved #219
Comments
Thanks @asteppke for the report. Would you be able to try with the new |
Using jupyter-collaboration v2.0.1 we are seeing similar problems. When this extension is added to our Docker environment, the Python notebooks within JupyterLab 4.0.11 lose the ability to click the save button in the notebooks as well as the |
This is expected.
This can happen if your file is automatically loaded when you open JupyterLab and the previous session was with RTC disabled. In this case, try closing the file and opening it again. |
Thank you so much for your response! This was tested in Binder so nothing had been previously opened, but I did try creating and opening a new notebook, closing and re-opening and it still did not have the ability to press the save button. Any other possibilities? You are welcome to test this out on Binder in this pull request I just made if you want to try it out. I'm also happy to just paste in a screen shot of it. |
This is the normal behavior, manual saving is disabled in collaborative mode, as the document is automatically saved after each change. |
Ah ok that makes sense. The autosave does seem to be working as expected. Thank you for identifying that for me! |
With good experiences we are now using the
jupyter-collaboration
extension (version 2.0.0a4) for a few weeks.Unfortunately, under some circumstances, and without apparent warnings severe data loss occurs. In this case one opens a notebook in jupyterlab, edits it and it gets automatically saved. This is indicated by the file modification time and the entries in the corresponding jupyterlab logfile:
After a break of several hours the connection is re-established to the notebook server, and further editing takes place. Now jupyterlab does not save the changes anymore from here on, any further input does only exist in memory. There is no warning or error from the UI side and if the server is shutdown the notebook does not contain any of the new input.
The logfile indicates a Tornado error but I am not certain if this is related. In any case no save events are logged or take place:
As far as I have observed everything starts out correctly and I do not know who to trigger the behavior explicitly. A disconnect and re-connect to the server after some time does seem to be correlated with it though.
At least a temporary workaround seems to be to explicitly use
Save Notebook As...
to save the notebook under a new file name, this re-starts the autosave functionality.How can this be debugged further?
Context
ystore
-database is set to be written to/tmp
because the notebook directory is on NFS and this caused troubles in the pastConda environment
The text was updated successfully, but these errors were encountered: