-
-
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
Connection lost after (about) one minute #366
Comments
Why are you using pre-releases of jupyter-collaboration and jupyter-ydoc? |
Thanks for reporting the issue. I opened jupyter-server/jupyverse#442 which allows configuring the document cleanup delay. It was indeed hard-coded to 60 seconds, that's why you were observing connection loss. To avoid that behavior, you will have to launch jupyverse with the new jupyverse --set kernels.require_yjs=true --set jupyterlab.server_side_execution=true --set yjs.document_cleanup_delay="inf" |
I released jupyverse v0.6.3. |
Hi, when using Jupyter-collaboration on Jupyverse, it seems that staying disconnected for more than about 60 seconds while computing causes the connection to the server to be lost. I’ve done some tests to confirm this. If the page is kept open, everything works fine. If you disconnect for 30 seconds, it works fine. If you stay disconnected for some minutes but the computation lasts for less than 60 seconds, it still works fine. But beyond about 60 seconds of computation in which you are disconnected, the connection that returns the output is lost. Is it possible that there’s an intrinsic timeout somewhere? I’m attaching a screenshot of what happens. I lunched the code, disconnected after few seconds and then reconnected after some minutes, in the first case the output is truncated, while in the second the output is fine.
Here my configuration (and thanks again for the help in setting this up).
The text was updated successfully, but these errors were encountered: