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
During a peering from the hub side the hub will wait 30s or a spdy ping before the connection is considered timed out. When this happens it closes the underlying ./lib/web_socket.js which the ./lib/peer_client.js expects a error/close event to propagate back to the peer_client from the web_socket.
In the case when the connection times out waiting for the http response from the websocket server in the cloud the error or close event never are emitted as the socket isn't estabiished yet and we do nothing herethis.socket is not set from here.
The text was updated successfully, but these errors were encountered:
During a peering from the hub side the hub will wait 30s or a spdy ping before the connection is considered timed out. When this happens it closes the underlying
./lib/web_socket.js
which the./lib/peer_client.js
expects aerror/close
event to propagate back to the peer_client from the web_socket.In the case when the connection times out waiting for the http response from the websocket server in the cloud the
error
orclose
event never are emitted as the socket isn't estabiished yet and we do nothing herethis.socket
is not set from here.The text was updated successfully, but these errors were encountered: