Open alloy opened 8 years ago
probably the one from socket?
perhaps a new exception would make sense... SocketNameResolutionError < SocketError
?
Sure, I can do that, and keep the same error message, yeah?
@ioquatix Like so?
Yeah that seems fine.
@tarcieri still waiting for travis issues to be fixed, boop :)
@ioquatix that was on nio4r. The test failures look like the same on master (we never got celluloid-io back to green)
ah okay I guess I'll take a look at the issues here.
In short, what I tried to fix is the following behaviour when trying to resolve a hostname when offline:
What happens is that
@socket
remainsnil
here which means that you end up sending the hostname as aNilClass#send
message here.With stdlib it raises the following exception, although that one is actually not raised by the name resolver, but by Socket:
The one raised by Resolv is:
I’m not sure which one I should use, any thoughts?