C
Chris Eppstein
This commit:
http://github.com/FooBarWidget/rubyenterpriseedition/commit/00a8c1b356b482b2b34931344e747062a8d07795
Breaks the documented API of the timeout function by changing the
default exception class raised from Timeout::Error to
Timeout::ExitException.
I spent a fair bit of time diagnosing this issue today as it was
causing misbehavior in memcache-client. As a work-around, I am using a
modified version of memcache-client that specifies Timeout::Error as
the timeout
exception class explicitly, but it would be great to fix this as I'm
sure lots of libraries expect Timeout::Error.
Thanks,
Chris Eppstein
P.S. I originally reported this issue to the Phusion guys, but they
directed me here.
http://github.com/FooBarWidget/rubyenterpriseedition/commit/00a8c1b356b482b2b34931344e747062a8d07795
Breaks the documented API of the timeout function by changing the
default exception class raised from Timeout::Error to
Timeout::ExitException.
I spent a fair bit of time diagnosing this issue today as it was
causing misbehavior in memcache-client. As a work-around, I am using a
modified version of memcache-client that specifies Timeout::Error as
the timeout
exception class explicitly, but it would be great to fix this as I'm
sure lots of libraries expect Timeout::Error.
Thanks,
Chris Eppstein
P.S. I originally reported this issue to the Phusion guys, but they
directed me here.