Skip Menu |
 

This queue is for tickets about the AnyEvent-RPC CPAN distribution.

Report information
The Basics
Id: 71148
Status: open
Priority: 0/
Queue: AnyEvent-RPC

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

Bug Information
Severity: (no value)
Broken in: 0.05
Fixed in: (no value)



Download (untitled) / with headers
text/plain 311b
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
Download (untitled) / with headers
text/plain 551b
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" }


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.