You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You kind of want to say “it’s timeing out, of course it fails”, but:
a) content in this scenario is documented to be a meaningful message, not CODE(0x20170e0) so it’s behaving contrary to documentation
b) if you debug a bit and find out what that coderef returns, it’s actually a full, valid looking, response object, suggesting that the response was complete and successful, not a timeout.
Perl is a little old:
This is perl 5, version 16, subversion 3 (v5.16.3) built for x86_64-linux-thread-multi
(with 44 registered patches, see perl -V for more detail)
Copyright 1987-2012, Larry Wall
Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
On CentOS 7.
The text was updated successfully, but these errors were encountered:
I get a broken looking internal exception when using with Time::Out:
Output:
You kind of want to say “it’s timeing out, of course it fails”, but:
a) content in this scenario is documented to be a meaningful message, not
CODE(0x20170e0)
so it’s behaving contrary to documentationb) if you debug a bit and find out what that coderef returns, it’s actually a full, valid looking, response object, suggesting that the response was complete and successful, not a timeout.
Perl is a little old:
On CentOS 7.
The text was updated successfully, but these errors were encountered: