#celery

asksol: http://pastebin.com/ibVZ1FfW this syntax is not compatible anymore?

it is, the task decorator defines task.run

you can verify that by doing add(2, 2), which should execute the decorated function

or add.run(2, 2)

So, is the task decorator defines a method named run, why i'm getting this exception?

*if

do you want to see the entire example?

asksol: http://pastebin.com/u5KhJq0x

If I use chain and subtask without registering the task on the celery_app I'll get this exception

italorossi: obviously the task can not be properly registered in the worker, or it is registered with an object that does not have a .run method

Did you saw the last pastebin link?

yes, but defining the task in the client does not have any effect on the worker, so you must be doing something wrong

I have no idea what's wrong.. but this code just works with the task defined on the client. Commenting out the tasks definition on the client generates NotImplementedError in the worker

italorossi: then maybe you're sending the wrong name? See the list of registered tasks at worker startup (needs -l info)

asksol: i've double checked, the names are correct.. (there is a minor copy/paste issue on the pastebin version, just ignore..)

asksol: Can you try running the example I've posted early?

I'll be back in a few hours

asksol: Hi, did you figured out what's wrong on that example?

asksol: This is the same problem as described here: https://groups.google.com/forum/#!msg/celery-us...

italorossi: you should submit an issue to github

asksol: sure, i'll submit right now! thanks

I will fix it soon, just very busy trying to prepare 3.1

asksol: nice! Let me know if there is something that I can do to help you

The What's new in Celery 3.1 document is taking form: http://docs.celeryproject.org/en/master/whatsne...

asksol: https://github.com/celery/celery/issues/1607

asksol: thanks for your time :)

thanks!

asksol: you there?

Diranged: hey! on and off

asksol: Hey… do you have a few mins to talk about the rate limiting system?

asksol: We've been going back and forth on it here at the office, and we're a little unsure about how parts of it work.

asksol: Imagine a scenario where we have a queue with 5000 EmailTasks and 2000 HelloWorld tasks all intermixed. We limit the EmailTasks to 10/minute and we leave no limit on the HelloWorld tasks. My understanding of the current system is that our celery workers will pull down a task (they dont know what they're getting until they get it, right?), and if its an EmailTask .. and if the rate that they're being sent is > 10/minute, that worker will hold the task

asksol: Am I correct about that?

sure, it must consume the message to know what task it is

to keep more tasks limits you have to increase the prefetch multiplier

keep more tasks in the worker*

who can tell me. my celery workers suddenly stop processштп tasks.

asksol: I'm about to submit an issue, but maybe you could squash it instead

basically I'm starting two workers, one processes and one gevent, but it doesn't work

celery multi says it started them OK but they are not running

if I do celery multi show I do not see the "start" arg printed out

if I add start and run each worker manually they run fine

even if I set the second worker to -P processes it still doesn't help

asksol: In the event that we have a worker pull down 10 tasks at a time via the prefetch, if it decides that Task #1 needs to be throttled, the code implies that the worker will block there on a sleep() timer. Right?

hey all - trying to receive task-sent events, can anyone give me some pointers?

here's my receiver code: https://gist.github.com/swinton/0a6f72ab84d7350...

And I've enabled CELERY_SEND_TASK_SENT_EVENT

But my handler isn't firing

Can't see what I'm missing. Any pointers?

Nevermind, it's all working. Just turned it all off and on again.

Wheeeeee :)