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 been using a system which uses a proxy and a certain VPN which closes idle connections after a certain timeout. Due to this the WebSocket connection to the jupyter server closes if no cells are run for a certain period and the state of the next cell run shows up as "Queuing", however if we check the Network Console, we find that a new WebSocket connection gets established and then re-running the cells works fine with the last run cell incorrectly showing the state as "Queuing" even though it runs fine. Is there any way to avoid the disconnection?
The text was updated successfully, but these errors were encountered:
I've been using a system which uses a proxy and a certain VPN which closes idle connections after a certain timeout. Due to this the WebSocket connection to the jupyter server closes if no cells are run for a certain period and the state of the next cell run shows up as "Queuing", however if we check the Network Console, we find that a new WebSocket connection gets established and then re-running the cells works fine with the last run cell incorrectly showing the state as "Queuing" even though it runs fine. Is there any way to avoid the disconnection?
The text was updated successfully, but these errors were encountered: