Closed andyscho closed 3 months ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
Related to or a duplicate of https://github.com/jupyterlab/jupyter-collaboration/issues/312
Description
When running with jupyterlab>=4.1.0, it is fairly common to hit the "FIle Changed" prompt in a RTC session when saving. An error like "Different hash found for RTC:notebook_name.ipynb" can also be present in the console.
This issue was only present when running jupyterlab with the jupyter-collaboration extension; it is not present when running jupyterlab without the jupyter-collaboration extension.
This video demonstrates this issue.
Reproduce
Follow the instructions for Installing JupyterLab Real-Time Collaboration, also pasted here:
Then install jupyterlab, e.g.
pip install jupyterlab==4.2.1
. I tested several different versions of jupyterlab. The lowest version I was able to reproduce the issue with was 4.1.0. The highest version I was not able to reproduce the issue with was 4.0.13. An examplepip freeze
that I used can be found here [1]. The only difference in the set of packages I tested different versions of jupyterlab was the jupyterlab version itself.Once jupyterlab is installed, run
jupyter lab
, open a notebook with RTC, and start editing and saving. You can also try holding down the hotkey to save if you want - I do this at one point in the video above. You should run into a "File Changed" error fairly quickly, though it might take some trying.Expected behavior
No "File Changed" errors when no actual outside file changes take place. Running RTC with Jupyterlab<=4.0.13 does not have this issue, at least not nearly as common or widespread.
Context
Reproducible on different filesystems on both mac and linux, as well as different chrome versions.
[1] Output of
pip freeze
(the only difference inpip freeze
output between different tests was the jupyterlab package version):