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
Not sure the root cause of why this started happening. It could either be a change in browser behavior or a change in Node or ws behavior. Either way, if we handle the error event on sockets, we can detect and safely ignore when this occurs. First reported in donejs/donejs#1064.
The text was updated successfully, but these errors were encountered:
Chrome 63 no longer closes its websocket connection cleanly, which
causes an error on the socket in the server.
This makes sure that we handle the error. Fixes#912
Not sure the root cause of why this started happening. It could either be a change in browser behavior or a change in Node or
ws
behavior. Either way, if we handle theerror
event on sockets, we can detect and safely ignore when this occurs. First reported in donejs/donejs#1064.The text was updated successfully, but these errors were encountered: