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
It seems that when the PC has a wifi connection that is disconnected but not disabled, the GUI is not able to consistently talk to the scratch process. There may be an unknown error, things stall, sometimes a connect error to the server. This may turn out to be a library fix, but it seems to only happen with the GUI at the moment (the self-tests for remote components work).
I suspect that the cause is a misbehaving network API call (possibly related to DNS) either in Poco, or windows itself, or something mishandled. It only happens with a disconnected wifi which is a good clue.
It seems that when the PC has a wifi connection that is disconnected but not disabled, the GUI is not able to consistently talk to the scratch process. There may be an unknown error, things stall, sometimes a connect error to the server. This may turn out to be a library fix, but it seems to only happen with the GUI at the moment (the self-tests for remote components work).
I suspect that the cause is a misbehaving network API call (possibly related to DNS) either in Poco, or windows itself, or something mishandled. It only happens with a disconnected wifi which is a good clue.
The text was updated successfully, but these errors were encountered: