You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In JupyterCAD and gluel-lab, we registered new document types with jupyter_ydoc to be able to modify them collaboratively.
If the document is opened in JupyterLab once, and then it is modified externally while JupyterLab is not running, the next time I open this document in Lab, the content is restored from the database. The only way to keep the new content is to remove the database in the current working directory.
From the server log, I believe this is the intention of jupyter_ydoc, but I feel like it creates a lot of confusion for a normal user. If there aren't technical constraints, I think we should allow users to disable this behavior or at least give them a warning before overwriting the file.
The text was updated successfully, but these errors were encountered:
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
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! 👋
In
JupyterCAD
andgluel-lab
, we registered new document types withjupyter_ydoc
to be able to modify them collaboratively.If the document is opened in
JupyterLab
once, and then it is modified externally whileJupyterLab
is not running, the next time I open this document in Lab, the content is restored from the database. The only way to keep the new content is to remove the database in the current working directory.From the server log, I believe this is the intention of
jupyter_ydoc
, but I feel like it creates a lot of confusion for a normal user. If there aren't technical constraints, I think we should allow users to disable this behavior or at least give them a warning before overwriting the file.The text was updated successfully, but these errors were encountered: