Re: Timeout::Error

Jim Hranicky wrote:
> Jeremy Thurgood wrote:
> 
>>> No.  The exception would be rescued inappropriately then.
>> At the moment it's being /not/ rescued inappropriately. Why should a 
>> timeout exception (from within the standard libraries!) evade a naked 
>> "rescue"? The current situation requires me to figure out everythign 
>> that can possibly time out and add special-case error handling for it. 
>> Worse than this, irb doesn't catch Timeout::Error and thus kills my 
>> session (which typically has a bunch of state in it) whenever the http 
>> server I'm talking to takes a while to respond.
> 
> While I tend to agree and ran into the same frustration as you, you can
> specify the type of exception Timeout throws like so:
> 
>    timeout(5, StandardError) { ... }
> 
> which seems to do what's desired,
> 
>      ruby -rtimeout -e 'begin ; timeout(5, StandardError) { while true; sleep 1; end }; \
>      rescue; puts "rescued" ; end'

Sure, if it's my code that's throwing the timeout. net/protocol.rb and 
net/http.rb aren't mine and I'm hesitant to monkey-patch them to throw 
different exceptions when I'm also using other libraries which use them.

A quick grep through /usr/lib/ruby/1.8 shows at least the following 
files using timeout without specifying a different exception to use:

ping.rb
webrick/httprequest.rb
net/telnet.rb
net/protocol.rb
net/http.rb

The only one that /does/ specify a different exception is resolv.rb, 
which throws a ResolvTimeout. This is a subclass of TimeoutError and 
thus suffers from the same problems.

--J

--