Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Redis CPAN distribution.

Report information
The Basics
Id: 57096
Status: resolved
Priority: 0/
Queue: Redis

People
Owner: melo [...] cpan.org
Requestors: dsrthorne [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.2001
Fixed in: (no value)



Subject: Deep recursion on subroutine "Redis::AUTOLOAD" at /usr/local/share/perl/5.10.0/Redis.pm line 150, <GEN0> line 99.
After making a connection with Redis->new to a *memcache* server running on the port, this is what I get when running any command: Deep recursion on subroutine "Redis::AUTOLOAD" at /usr/local/share/perl/5.10.0/Redis.pm line 150, <GEN0> line 99. Sample code to reproduce: my $redis = Redis->new(server => "$redis_host:$redis_port", debug => 1); print Data::Dumper($redis); print "Calling ping\n"; if ($redis->ping) { print "Redis->ping returned true\n"; } else { print "Redis->ping returned false\n"; } exit(0); Output: $VAR1 = bless( { 'debug' => 1, 'server' => 'localhost:31211', 'sock' => bless( \*Symbol::GEN0, 'IO::Socket::INET' ) }, 'Redis' ); Calling ping ## ping at /usr/local/share/perl/5.10.0/Redis.pm line 88. Show quoted text
>> PING
<< ERROR ## __read_line at /usr/local/share/perl/5.10.0/Redis.pm line 88, <GEN0> line 1. Show quoted text
>> __READ_LINE
<< ERROR ## __read_line at /usr/local/share/perl/5.10.0/Redis.pm line 88, <GEN0> line 2. Show quoted text
>> __READ_LINE
<< ERROR ## __read_line at /usr/local/share/perl/5.10.0/Redis.pm line 88, <GEN0> line 3. Show quoted text
>> __READ_LINE
<< ERROR ## __read_line at /usr/local/share/perl/5.10.0/Redis.pm line 88, <GEN0> line 4. Show quoted text
>> __READ_LINE
<< ERROR
To be clear, what I'm looking for here is a more graceful failure when the responses aren't exactly what you expect. Error checking ftw.
Hi, I don't have a memcached server handy to test this, but all the protocol parsing code was re- written for the 1.901 release, and this problem might be solved already. Could you please test this latest release? In the meantime, I'll look over the parsing code to see if we can make it more reliable. Thanks,
I'm closing this for now, I assume that the problem is solved. Please reopen if you still find a problem with the new code. Thanks, -- Hi, how are you?