Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Gearman CPAN distribution.

Report information
The Basics
Id: 59185
Status: resolved
Priority: 0/
Queue: Gearman

People
Owner: info [...] maximka.de
Requestors: ktdreyer@ktdreyer.com (no email address)
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.11
Fixed in: 1.130.001



Subject: document Gearman::Client::get_status
dispatch_background's documentation explains that you will receive a job handle scalar, but it doesn't explain what to do with this. get_status() is in the code, but not in the documentation. I've written a small paragraph for this function. =head2 $client-E<gt>get_status($jobhandle) The Gearman Server will assign a scalar job handle when you request a background job with dispatch_background. Save this scalar, and use it later in order to request the status of this job. Return value is a I<Gearman::JobStatus> object.
From: ktdreyer [...] ktdreyer.com
This bug exists in 1.11, and here is a patch against http://code.sixapart.com/svn/gearman/trunk/api/perl/Gearman/
Subject: get-status-docs.patch
Index: Gearman/lib/Gearman/Client.pm =================================================================== --- Gearman/lib/Gearman/Client.pm (revision 483) +++ Gearman/lib/Gearman/Client.pm (working copy) @@ -478,8 +478,15 @@ =head2 $client-E<gt>dispatch_background($funcname, $arg, \%options) Dispatches a task and doesn't wait for the result. Return value -is an opaque scalar that can be used to refer to the task. +is an opaque scalar that can be used to refer to the task with get_status. +=head2 $client-E<gt>get_status($jobhandle) + +The Gearman Server will assign a scalar job handle when you request a +background job with dispatch_background. Save this scalar, and use it later in +order to request the status of this job. Return value is a +I<Gearman::JobStatus> object. + =head2 $taskset = $client-E<gt>new_task_set Creates and returns a new I<Gearman::Taskset> object.
it will be solved in v1.130.001
v1.130 is released