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, in the current version (7.2.1) an older bug similar to #1564 seems to have reappeared:
node_modules/ws/lib/websocket.js:837
websocket.readyState = WebSocket.CLOSING;
TypeError: Cannot set property 'readyState' of undefined
at Socket.socketOnClose (node_modules/ws/lib/websocket.js:837:24)
at Socket.emit (events.js:333:22)
at Socket.EventEmitter.emit (domain.js:485:12)
The text was updated successfully, but these errors were encountered:
The issue was caused by an invalid usage of ws, so my guess is that you are doing the same mistake. Are you using gun.js? If so see #1606 and #1606 (comment) in particular.
Please fill the issue template, it's there for a reason, and create a test case to reproduce the issue.
Yup, you're right. I do not use gun.js, but there were two WebSocket servers created for the same http server.
Maybe ws can check if there is already an instance attached to a http server?
Closing this as it is not a bug.
Hi, in the current version (7.2.1) an older bug similar to #1564 seems to have reappeared:
The text was updated successfully, but these errors were encountered: