Skip Menu |

This queue is for tickets about the POE CPAN distribution.

Report information
The Basics
Id: 18646
Status: resolved
Priority: 0/
Queue: POE

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

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



Subject: POE::Kernel::alias_resolve() throws a fatal error under ASSERT_RETVALS
Under POE_ASSERT_DEFAULT=1, (and as it turns out, under ASSERT_RETVALS), if $kernel->alias_resolve() does *not* resolve to a session, it throws a fatal exception, instead of simply warning. This patch fixes it in 0.3401
Subject: alias_resolve_fatal.patch
--- Kernel.pm~ 2006-04-10 15:54:57.000000000 -0700 +++ Kernel.pm 2006-04-10 17:02:36.000000000 -0700 @@ -623,8 +623,8 @@ } $! = ESRCH; - TRACE_RETVALS and _carp "<rv> session not resolved: $!"; - ASSERT_RETVALS and _confess "<rv> session not resolved: $!"; + TRACE_RETVALS and _carp "<rv> session not resolved: $!"; + ASSERT_RETVALS and _carp "<rv> session not resolved: $!"; } ### Explain why a function is returning unsuccessfully.
From: rdb [...] cpan.org
On Mon Apr 10 20:31:31 2006, guest wrote: Show quoted text
> Under POE_ASSERT_DEFAULT=1, (and as it turns out, under ASSERT_RETVALS), > if $kernel->alias_resolve() does *not* resolve to a session, it throws a > fatal exception, instead of simply warning. > > This patch fixes it in 0.3401
Now that I think about it, is that warning even needed under ASSERT?
You're right. alias_resolve() should not throw errors or traces if an alias fails to resolve. The asserts and traces have been removed. Thanks for the bug report and patch.
Re-resolving it. RDB reopened it without a note.
On Sat Sep 16 02:19:16 2006, RCAPUTO wrote: Show quoted text
> Re-resolving it. RDB reopened it without a note.
He actually reopened it because his patch was never applied.
Should be fixed in POE-0.38 -- ~Apocalypse