Skip Menu |

This queue is for tickets about the IO-Async CPAN distribution.

Report information
The Basics
Id: 103921
Status: resolved
Priority: 0/
Queue: IO-Async

People
Owner: Nobody in particular
Requestors: TEAM [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.66
Fixed in: 0.69



Subject: Oops; $loop->connect failed but no error cause was found
Seeing this error when providing invalid addr data, presumably something's losing the real message along the way: $ perl 2015-04-24-io-async-oops.pl Oops; $loop->connect failed but no error cause was found at .../IO/Async/Internals/Connector.pm line 152. I *think* this is recent, will try with earlier versions to confirm. cheers, Tom
Subject: 2015-04-24-io-async-oops.pl
#!/usr/bin/env perl use strict; use warnings; use IO::Async::Loop; my $loop = IO::Async::Loop->new; my ($conn) = $loop->connect( addr => { host => '127.0.0.1', service => 80, socktype => 'stream', }, )->get;
On Thu Apr 23 20:53:23 2015, TEAM wrote: Show quoted text
> Seeing this error when providing invalid addr data, presumably > something's losing the real message along the way:
Ah; interesting. Connect in this manner is likely to fail in a very odd way. By setting the addr key, you're saying you provide an AF_INET address here; yet the string probably isn't valid formatting. I wonder if this causes upsets at the kernel level... -- Paul Evans
This was fixed in 0.69 to avoid losing the actual failure message. Whatever failure case still exists, but at least the message remains now. -- Paul Evans