-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Documents won't open after a user's session expires and renews. #290
Labels
bug
Something isn't working
Comments
Thanks Zach for opening this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I ran into an issue where the JupyterLab becomes completely blocked from opening any documents when a user's cookie expires. Even after being re-authenticated and refreshing the page, I am unable to open any documents. The only thing that unblocks this scenario is to restart the server.
To help debug the issue a bit, I'll give a summary of what I saw in the logs (sorry for the ugly JSON, it's what I have running 😅 ) with timestamps.
The user cookie expires.
Due to expiration, the JupyterLab lost connection to the server and I think this caused the document to self clean.
The client is still trying to poll the server using an expired token, so a bunch of 403s appear. I'll include the first one here
and the last one here to show time-stamp differences. About 1 minute passed with polling happening every ~3 seconds.
After polling for a minute, the y document self deleted itself.
The server has deleted the room, but the (unauthenticated) client still thinks it's there, so it sends the old (deleted) ID to the server. There is definitely a bug here already... this endpoint should be authenticated but it doesn't appear to be.
The final UX is that the document never opens. Just a spinning wheel shows.
The text was updated successfully, but these errors were encountered: