ENOTFOUND and ECONNRESET errors

[defunctzombie]

I will switch to anything that gives me better debug info when these two errors happen. Please just put the domain or IP or something in the message :)

[MauriceButler]

I agree. ETIMEDOUT is another one.

I have done a few hacks to work around and get some stack in these instances but I would love to "fix" them once and for all.

Once the contributing stuff ( #20 ) has been confirmed I might try to find some time to resolve.

[MauriceButler]

@defunctzombie I had a quick look and the usage of these codes is a bit all over the place. Might take a bit to actually come up with a good fix.

In the meantime you can do something like this to give some additional debugging info when these errors occur. https://github.com/MauriceButler/request-callback-wrapper/blob/master/index.js

Ill have another look on the weekend and try to work something out.

[caineio]

Hello!

I am pleased to see your valuable contribution to this project. Would you
please mind answering a couple of questions to help me classify this submission
and/or gather required information for the core team members?

Questions:

1. Issue-only Does this issue happen in core, or in some user-space
   module from npm or other source? Please ensure that the test case
   that reproduces this problem is not using any external dependencies.
   If the error is not reproducible with just core modules - it is most
   likely not a io.js problem. Expected: yes
2. Which part of core do you think it might be related to?
   One of: debugger, http, assert, buffer, child_process, cluster, crypto, dgram, dns, domain, events, fs, http, https, module, net, os, path, querystring, readline, repl, smalloc, stream, timers, tls, url, util, vm, zlib, c++, docs, other (label)
3. Which versions of io.js do you think are affected by this?
   One of: v0.10, v0.12, v1.0.0 (label)

Please provide the answers in an ordered list like this:

1. Answer for the first question
2. Answer for the second question
3. ...

Note that I am just a bot with a limited human-reply parsing abilities,
so please be very careful with numbers and don't skip the questions!

In case of success I will say: ...summoning the core team devs!.

In case of validation problem I will say: Sorry, but something is not right here:.

Truly yours,
Caine.

Responsibilities

1. indutny: crypto, tls, https, child_process, c++
2. trevnorris: buffer, http, https, smalloc
3. bnoordhuis: http, cluster, child_process, dgram

[cjihrig]

@defunctzombie since #35 has been merged, is this OK to close?

[defunctzombie]

😍