gbarr / perl-beanstalk-client Goto Github PK

Occurs with perl 5.20.x and 5.24.0 on Mac OS X. Seems to be related to automated dependency check (line 24).

Occurs only when beanstalkd is running.

I'm not sure if this is because I'm running it on a mac, but adding "use Beanstalk::Client;" to any program results in this error:

Attempt to free unreferenced scalar: SV 0x1008fb1c8 at /data/apps/lib/perl5/site_perl/5.12.3/Beanstalk/Client.pm line 528.

I'm using perl 5.12.3 on Mac OX 10.7.5.

Everything seems to function just fine.

Any thoughts?

Hi there,
Im using perl 5.14, and im trying to install the module with cpan, i got a problem with this:
cpan[4]> install Beanstalk::Client
Running install for module 'Beanstalk::Client'
Running make for G/GB/GBARR/Beanstalk-Client-1.07.tar.gz
Has already been unwrapped into directory /root/.cpan/build/Beanstalk-Client-1.07-CW4T40
Has already been made
Running make test
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/00-client.t t/01-job.t t/02-command.t
t/00-client.t ... ok
t/01-job.t ...... 1/44

This test doesnt permit to continue the installation.
Cheers.

Hi,

We've just installed the beanstalkd queue system and are using your Perl client library, thanks very much for it.

We've actually implemented quite a lot in less than 24 hours using both your library and beanstalk, its rather impressive as to what can be done.

One utility we were trying to write was something to clear all the tubes out. We've been throwing tens of gigabytes of data into the system to see how it stresses and it seems to handle X0,000 messages each of 5-10MB without causing any issues. Rather than processing the messages, we thought we'd delete them directly from the tubes.

As far as we can see we need the job id to be able to delete something from the tubes without processing it, but we can't see anything in your perl client to get the job id.

We've looked in the beanstalkd protocol docs and can see this

Other Commands
--------------

The peek commands let the client inspect a job in the system. There are four
variations. All but the first operate only on the currently used tube.

 - "peek <id>\r\n" - return job <id>.

Your Perl code for the peek command seems to want to have the job id passed into it, rather than returning it. We've looked at your Perl code as well and can see that it is expecting an argument to be passed in.

Have we misunderstood the point of your peek code? is there an other way of getting the job id?

We know we can write expect scripts onto telnet session, but thats rather an 1980's day of doing things. We'd much rather use Perl than try to remote how expect works :)

Thanks again,

Rob

Hi Graham,

Just wondering if you got the chance to implement multi beanstalkd server functionality?

Thanks,
Chris