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
Hi there, I am using this library on a fairly large project and recently we had an incident where the assertIsWebsocket assertion started failing.
We were unable to track down the cause of the failure, and bypassing the assertion with skipAssertion: true fixed the issue. We suspect that some sort of network change may have been the culprit, but was hoping you might be able to shed some light on what the purpose of the assertion is and why a socket that is NOT an instanceof WebSocket would still be able to function correctly.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi there, I am using this library on a fairly large project and recently we had an incident where the assertIsWebsocket assertion started failing.
We were unable to track down the cause of the failure, and bypassing the assertion with skipAssertion: true fixed the issue. We suspect that some sort of network change may have been the culprit, but was hoping you might be able to shed some light on what the purpose of the assertion is and why a socket that is NOT an instanceof WebSocket would still be able to function correctly.
Thanks!
The text was updated successfully, but these errors were encountered: