Re: Timeout::Error

Kurt Stephens wrote:
>   Since Timeout exceptions are an explicit and expected part of a
> program's behavior, it makes sense to distinguish them from typically
> unexpected errors (i.e. StandardError).  The net libraries should
> probably be fixed rethrow its own Timeouts into some API-specific
> subclass of Exception.  The only thing that is "exceptional" about
> Timeout errors is the delivery mechanism.

This would be fine if a blanket "rescue" caught them. It doesn't, which 
is why I have this issue in the first place.

To me, StandardError is the superclass for /recoverable/ exceptions (not 
unexpected ones), which timeouts typically are. Looking at some of the 
other exception classes, ScriptErrors typically require changing code, 
except in certain  rare applications. SignalExceptions (I would hope) 
are thrown only for things like SIGINT and SIGTERM which are external to 
the application and have pretty well-defined behaviour in the absence of 
explicit handling.

> If irb is not trapping Timeout, it's broken,
> APIs that leak Timeouts are broken,
> Ruby is not broken.

Timeout is broken, not Ruby. irb not handling it is a symptom, not the 
problem.

--J

--