Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upSocket hang up error upon stream reconnect #117
Comments
This comment has been minimized.
This comment has been minimized.
|
Closing this - some of the reconnect logic has been fixed. If you still see this with twit v |
ttezel
closed this
Feb 21, 2015
This comment has been minimized.
This comment has been minimized.
MeanwhileMedia
commented
Apr 28, 2015
|
Sounds good thanks @ttezel |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
MeanwhileMedia commentedJun 7, 2014
I close, then reopen a streaming api connection about every 10 minutes. The reconnects were working fine until I updated to node v0.10.28. Now I get socket hang ups when I try to reconnect, which result in a fatal error:
The initial connection is working fine. It is the disconnect/reconnect that breaks things.
I'm also noticing that node-oauth (through twit) is attempting to open new connections at seemingly random times with no explanation or reason. Some things definitely seem to be off with twit and the newest version of node.
@ttezel, everything still working alright on your end? Have you had the chance to do any testing on the newest version of Node? Do you think this is an issue with node-oauth? I opened an issue in the node-oauth repo as well which has additional details: ciaranj/node-oauth#199
I'm using twit 1.1.15 (current version)
thanks