Bug #71148 for AnyEvent-RPC:

Thu Sep 22 07:29:38 2011 NPW [...] cpan.org - Ticket created

I've only made a cursory examination of the code, since I was simply wondering how you handled error conditions within AnyEvent. However, AnyEvent::RPC appears to call rpcfault, without defining it. http://search.cpan.org/grep?cpanid=MONS&release=AnyEvent-RPC-0.05&string=rpcfault&i=1&F=1&n=1&C=0 Cheers, N

Fri Sep 23 11:23:06 2011 MONS [...] cpan.org - Correspondence added

On Thu Sep 22 07:29:38 2011, NPW wrote: Show quoted text

> I've only made a cursory examination of the code, since I was simply > wondering how you handled error conditions within AnyEvent. > > However, AnyEvent::RPC appears to call rpcfault, without defining it. > > http://search.cpan.org/grep?cpanid=MONS&release=AnyEvent-RPC- > 0.05&string=rpcfault&i=1&F=1&n=1&C=0 > > Cheers, > > N

Thanks, I'll fix it. That code was derived from somewhere... of course it should be {fault=>{ faultCode => $res->code, faultString => "Call to $req{uri} failed: $status" }

Fri Sep 23 11:23:07 2011 The RT System itself - Status changed from 'new' to 'open'