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
I've not been able to pinpoint the reason, but it seems like the initial attempt to connect to a VNCserver via websockets when visiting /desktop can sometimes fail. I suspect its a race condition that may make it never happen in some contexts, and often in others.
In #101 there is now a test that often but not always in our CI system on the first attempt, but not the second.
Debugging
I've not reproduced this by visiting /desktop on my laptop for tiger or turbo, but I think it does from my desktop computer
Reproduced using dockerspawner, as seen on the fourth attempt in this GIF:
The text was updated successfully, but these errors were encountered:
I've seen this show up more consistently when the ping is notable (by testing against a hub deployed in USA from Sweden). Three out of three tests made this happen on first attempt to visit /desktop, while doing things locally I just observed it one out of four for example.
I've not been able to pinpoint the reason, but it seems like the initial attempt to connect to a VNCserver via websockets when visiting /desktop can sometimes fail. I suspect its a race condition that may make it never happen in some contexts, and often in others.
In #101 there is now a test that often but not always in our CI system on the first attempt, but not the second.
Debugging
The text was updated successfully, but these errors were encountered: