Socket hang up about node-twitter HOT 5 CLOSED

Did you ever fix this? I have the same problem.

from node-twitter.

Hi @michaelmcmillan,
I couldn't really find the error.
What was causing it to happen more often was that my URL was sometimes malformed, due to some error in my coding. However, now that that's fixed, it still throws the error after longer periods (usually several days).
I did try to add error callbacks everywhere I could think of, still I couldn't catch the error.
I ended up using forks and domains for resiliency: http://nodejs.org/api/domain.html not the nicest solution, as I'd love to be able to handle this, but couldn't find any other way.
Please let me know if you find a solution!

from node-twitter.

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!

from node-twitter.

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.
Cheers.

from node-twitter.

No problem Ezequiel!

On Tue, May 27, 2014 at 3:58 PM, Ezequiel Rabinovich <
[email protected]> wrote:

Closed #18 #18.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/18#event-125105666
.

from node-twitter.