Skip Menu |

This queue is for tickets about the POE-Component-Client-Keepalive CPAN distribution.

Report information
The Basics
Id: 65275
Status: resolved
Priority: 0/
Queue: POE-Component-Client-Keepalive

People
Owner: Nobody in particular
Requestors: icabrera [...] cpan.org
Cc: i.arbeca [...] gmail.com
AdminCc:

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



CC: i.arbeca [...] gmail.com
Subject: Use of uninitialized value in delete
Hello, I got these errors while using Gungho module, which relies on POE::Component::Client::Keepalive : Use of uninitialized value in delete at /usr/local/perl-dists/perls/perl-5.12.2/lib/site_perl/5.12.2/POE/Component/Client/Keepalive.pm line 552. Use of uninitialized value $id in delete at /usr/local/perl-dists/perls/perl-5.12.2/lib/site_perl/5.12.2/POE/Component/Client/Keepalive.pm line 43. Use of uninitialized value $request_key in hash element at /usr/local/perl-dists/perls/perl-5.12.2/lib/site_perl/5.12.2/POE/Component/Client/Keepalive.pm line 679. Best Regards, Isabelle Cabrera
Hello, Thanks very much for reporting this! I've looked at the code and this sure is bizarre. The request id should never be undefined... Have you updated to the latest POE/Gungho/Keepalive dists? Have you talked to the Gungho author about this? Maybe they know about the problem and the bug actually is in their code and not Keepalive? I've looked at the Gungho distribution and it sure is a big beast. Do you have a small test case we can run to further troubleshoot this? If you can reliably reproduce it with Gungho that will be fine too. Please let us know, and we definitely can work with the Gungho authors to resolve this :) Thanks again! -- ~Apocalypse
Thank you for your answer. I just submitted a ticket to Gungho module : https://rt.cpan.org/Ticket/Display.html?id=65323 Unfortunately I am not able to reproduce this bug and this trace is all I have. Best regards Isabelle C
I'm afraid the line numbers have all changed. Please respond with new line numbers if you encounter this again?
Le Dim 20 Fév 2011 22:41:04, RCAPUTO a écrit : Show quoted text
> I'm afraid the line numbers have all changed. Please respond with new > line numbers if you encounter this again?
Thank you, I will upgrade the module and report if I encounter these errors.
On Mon Feb 28 03:38:16 2011, ICABRERA wrote: Show quoted text
> Le Dim 20 Fév 2011 22:41:04, RCAPUTO a écrit :
> > I'm afraid the line numbers have all changed. Please respond with new > > line numbers if you encounter this again?
> > Thank you, I will upgrade the module and report if I encounter these
errors. Is it safe to assume that no report means no errors?
Show quoted text
> Is it safe to assume that no report means no errors?
I didn't encounter these errors again but I don't know if there is any side effect to this. I actually dropped the use of Gungho, which depends on this module, so I can no longer make tests. Gungho didn't make an efficient use of POE and its author doesn't answer to bug requests. Best regards, Isabelle
Thank you for the bug report, and thanks for following up after all this time. I'm going to consider this resolved for now, because nobody else seems to have seen the same problem. If someone does encounter the problem, I hope they open a new ticket, and we'll begin again.