Handle server connection failures gracefully

[akavlie]

When an invalid server name is passed to node-irc, my app crashes as follows:

node.js:134
        throw e; // process.nextTick error, or 'error' event on first tick
        ^
Error: ETIMEDOUT, Operation timed out
    at Socket._onConnect (net.js:601:18)
    at IOWatcher.onWritable [as callback] (net.js:186:12)

[akavlie]

Sometimes, the error is as follows:

events.js:45
        throw arguments[1]; // Unhandled 'error' event
                       ^
Error: ENOTFOUND, Domain name not found
    at IOWatcher.callback (dns.js:74:15)

[bpaf]

I stumbled upon a third kind: see issue #76

[akavlie]

Is this still happening after my pull request? Are you using the github master branch, or release 0.3.3?

[bpaf]

I'm using the current npm release which is indeed 0.3.3. As you can imagine, this connection issue is quite painful to test, I will do my best to try tho.

[akavlie]

Yeah, I submitted some code which has been merged in on github, but hasn't yet been released on npm. Try out the latest rev in the master branch and see if that works.

[martynsmith]

I'm not sure if this is resolved or not. But since there hasn't been any activity for a very long time, I'm going to close this issue.

If anyone still experiences problems with it, feel free to re-open, or create a new issue.