-
Notifications
You must be signed in to change notification settings - Fork 237
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
Socket hang up #18
Comments
Did you ever fix this? I have the same problem. |
Hi @michaelmcmillan, |
Thanks for the swift reply! I also discovered that the errors were a result of my code sending in malformed data (specifically Object where it should have been an array). I still have not had the chance to see it running over a longer period, it remains to be seen if it dies. I'll keep you posted if it crashes. Thanks again! |
Great! Btw, i just checked, and in about 2 months running this only happened once, so it shouldn't be that much of a problem, I'll close the issue as now I can't really be sure it's caused by this library. |
No problem Ezequiel! On Tue, May 27, 2014 at 3:58 PM, Ezequiel Rabinovich <
|
Hi,
I'm using the Streaming API, and got this error a couple of times:
I'm handling the stream.on 'error' event, so I'm unsure if I'm missing something on my end or if there's an error not being handled by the library. The error happens sporadically, so it's hard to debug/reproduce.
I tried looking in the code, but didn't yet find anything that might be causing this, any ideas?
The text was updated successfully, but these errors were encountered: