-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: Object #<WebSocket> has no method 'payload' #523
Comments
got steps to reproduce? |
No idea how this happened, just got a huge number of connections (around 10K) . will see if I can get it again. |
+1 for this, same exception, same traceback. |
+1, we've been getting this randomly recently, even with very few connections. Same backtrace, slightly different line numbers:
|
It must be using the hybi-07-12 transport, which doesn't provide the payload method. It looks like WebSocket#payload is used exclusively for writing messages that were dispatched after a client is closed, once its been reopened. I'm ignorant about WebSocket implementations, but is there any reason why hybi-07-12 can't handle those in a similar way? If not, maybe the WebSocket#payload method for hybi-07-12 should be a noop. |
Ok, confirmed and fixed this. Will open a pull req after fixing another issue as well. |
Because WebPack does not support variables in require statements. Closes #522
The text was updated successfully, but these errors were encountered: