-
Notifications
You must be signed in to change notification settings - Fork 7
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
Connecting to server from notebooks-ui during spawn results in 500 #41
Comments
Maybe this is the cause:
|
That should've been fixed, where are you running it? This only happens when you enter the url manually |
I think the reason is that JH returns a 400 somewhere that isn't being handled properly |
Just to say, this is low priority imho. It's quite rare to click on connect while the server is spawning. |
sure, but to clarify -- you clicked connect in the "notebook UI" where it lists the running servers, right? That whole setup needs to be fixed, but yes, I think I've also encountered it there. |
yep |
For some reason, JH tries to spawn the server again when you try to connect:
This second spawn is after the first spawn is underway. Note the empty
Where this second spawn comes from I have no idea. I guess it could happen if JH automatically spawns a new server on a |
Leaving this open but removing it from the |
I believe it has been fixed with the new UI implementation. |
Clicking on
Connect
while the server is not ready results in a 500 page on jupyterhub.The text was updated successfully, but these errors were encountered: