-
Notifications
You must be signed in to change notification settings - Fork 28
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
[Yjs] Stateful file manager for yjs #247
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
This issue should be mitigated with the file ID service. There is an open PR in jupyverse. |
This is a history management issue, and a single It seems to me that single disks on Linux platforms can use I'm trying to implement a multi-user real-time collaborative data analysis service, but it may look similar to the problems Jupyter is currently facing but is different in nature |
Problem
For example, if you create a new ipynb (Untitled.ipynb), write something and rename it, and then create another ipynb (Untitled.ipynb), the new Untitled.ipynb will not open on the front end...
Proposed Solution
A file open and close related management should be added, yjs websocket connection can be seen as a file open, the crdt algorithm to solve the conflict of multiple users editing at the same time, when no user open the file, the file should be returned to "non-collaborative state"
This means that the life cycle of the file editing db should be bound to the user's access.
Also, I haven't figured out how to handle it when the service restarts or crashes, so maybe it needs an elegant startup to go with...
Additional context
This problem may also be related to the horizontal scaling of the jupyverse
The text was updated successfully, but these errors were encountered: