#celery

no one?

the task decorator converts the method into an object

you probably don't want to call that method synchronously anymore

and if you do celery provides an option for that called CELERY_EAGER (mainly for testing purposes)

Lobosque: ^

bmbouter I was calling it with delay. I had to name the arguments and it worked fine. now I am getting a "Worker exited prematurely" error when I retry my task =/

your worker is probably experiencing an exception

you should still call it synchronously for delay, but use a remote debugger to interactivly the asynchronous code

Lobosque: celery provides one for this if you don't have one you normally use for remote python debugging

I will look into it

but

i have a "catch all" in my task, so that's weird... Wasn't it supposed to catch this exception?

I'm not sure what is producing the "Worker exited prematurely" exactly, but interactivly debugging would provide more concrete information

you could also try to minimize the amount of code in there that is needed to reproduce that error message

hey all

I have an issue after migrating from Celery 3.0 to 3.1.x in combination with Django

I'm seeing a PRECONDITION_FAILED on the results

PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'celeryresults' in vhost 'xxxxx': : received 'true' but current is 'false'", (40, 10), 'Exchange.declare')

can anyone give me some pointers on what I'm doing wrong?

Ok, found the solution

seems the exchange was created without the durable option set but that's the default expected by Celery

Lobosque: if you use bind=True the task will be bound to the instance so self is not required

given that you use a version that actually supports bind=True

and don't use some kind of custom task decorator that is not delegating to the built-in one

Hello. I'm using django-celery with Django 1.7.7. Everything works fine, except when I try to run migrations: django.core.exceptions.ImproperlyConfigured: Application labels aren't unique, duplicates: djcelery

Any hints about this issue?

lskbr: are you sure you are running the latest version of kombu?

(it's a dependency of celery)

I can check that. I'm running exactly the same versions of the same app in 2 different machines, but I only got that error in one of them. I will double check kombu

I'm running kombu (3.0.26)

I'm running celery (3.1.18) django-celery (3.1.16) and kumbu (3.0.26)

I do not understand why I only have it: django.core.exceptions.ImproperlyConfigured: Application labels aren't unique, duplicates: djcelery when running migrations

I found a django bug, but it is supposed to be already solved on 1.7.7

hey all, question for everyone…I have a group thats' been apply_async()'d and the result object never shows ready() == True, completed_count() is always 0 and children shows all tasks in a PENDING state. Does anyone have any idea why this might be?

is there a way to use timedelta AND crontab together somehow? i want to execute a task every random.randomint(10,50) seconds between the hours of 6-23..

looks like the answer to my question is….I wasn't paying attention. thanks y'all! :)