-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Editing Jupyter Notebook in RTC mode will not update checkpoint, keeps changing to "not trusted" and reverts to previous state #197
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
Hello, I hope this message finds you well. I've been closely following the ongoing issue, and it seems like it hasn't been resolved yet. I'm more than willing to step in and take over resolving it. Please consider assigning me to the task, and I'll do my best to ensure a swift and effective resolution. Thank you for your attention to this matter. Best regards, |
I think checkpointing should be disabled altogether in RTC, since there is the same kind of functionality in the YStore (by default, a |
We are experiencing similar issues from multiple users when using Jupyterlab in RTC mode:
The issues happened intermittently and we haven't found a way to reproduce it. Given that they were also reported previously by multiple people, can you prioritize the investigation? Context: Jupyterlab 3.6.5 |
Checkpoints are not used when RTC is enabled. Are you mixing RTC and non-RTC modes in any way? |
Hey all, I am also having the same issue. It is quite problematic as it makes us loose data and code. We are running jupyterlab in on a jupyterhub server running Fedora. Sometimes the files become so long that the computer struggles to open them. I am not sure whether this is related, but jupyterlab always asks whether you want to override the file on the disk. I tried to change the delay accepted for modification date. Unfortunately without success. Thanks in advance for you help! |
Description
When editing a notebook with RTC enabled, the notebook will randomly revert to the last checkpoint (which was 7 days ago in this case) and all changes since then are lost. Neither Edit -> Undo or CTRL+Z will restore changes. Running my notebook requires VPN connection which I think might be part of the problem as the notebook will periodically change from "trusted" to "not trusted". When I then go to File -> Trust Notebook, it says something about the version I have open is not the same as the one on disk and asks me if I want to revert to the last checkpoint or overwrite the copy on disk. I always opt to overwrite with the version I have open, yet the checkpoint does not update and the issue persists. There seems to be no way to manually save the notebook other than downloading and re-opening it. I've opened and edited the document at some point in JupyterLab and not had this exact problem, but in doing this I have noticed another strange bug where I'll close and shut down the notebook, and upon reopening it, all cells in the notebook are duplicated (as in cells 1-20 appear, then at the end of the notebook there's cells 1-20 again). I've also copied a link to the document and opened it in an Incognito browser (Google Chrome) to test RTC when I first enabled it, but I closed and shut down the notebook before closing the browser.
Reproduce
I can't seem to figure out exactly what I'm doing to cause this behavior but here is essentially what's happened:
Context
Operating System and version: Microsoft Windows [Version 10.0.19044.3086]
Browser and version: Chrome Version 116.0.5845.188
IPython : 8.15.0
ipykernel : 6.25.2
ipywidgets : 8.1.0
jupyter_client : 8.3.1
jupyter_core : 5.3.1
jupyter_server : 2.7.3
jupyterlab : 4.0.5
nbclient : 0.8.0
nbconvert : 7.8.0
nbformat : 5.9.2
notebook : 7.0.3
qtconsole : 5.4.4
traitlets : 5.9.0
Related/similar issues:
jupyterlab/jupyterlab#10852
jupyterlab/jupyterlab#11348
jupyter/notebook#484
#163
Cross-listed here:
jupyter/notebook#7065
The text was updated successfully, but these errors were encountered: