#celery

anyone here ?

Hi, I'm looking for a option for manual ack sending after finishing the task, is it possible with the current version of the celery ( 3.11 and above ) ?

I didn't see any documentation regarding that.

haridas1, hmm, late acks don't work for you then?

Nanonyme: Nope: I want full control, since I can't lose the message if the task executed successfully. ie; It will decided by the coming message from Queue, that's why I'm looking for manual ack sending after successful operation, otherwise wise I will this message will handled after an interval.

Sorry... for the typos. "Otherwise the message will be handled by another task after an interval. "

hey all

I

I have a problem with chords not being unlocked properly and continuing forever. I'm using memcached as the results backend. Is it correctly understood that memcached gets restarted, or some information is lost, that can cause this behaviour?

pull requests should be done from master or the 3.0 branch ?

another question: is it possible to have chord_unlock run in a non-default queue?

nanonyme: Is using the ETA would solve it ?

In celery 3.0.17 if I create a task out of a method (using celery.contrib.methods.task) is the assumption that the object will be instantiated with no arguments passed to its constructor (__init__() method?)

asksol: before i go to much work on this, you dont already track the task creation time in the Task constructor, right?