#celery

Hi

Hi guys. Is anybody here? Want to discuss one minor bug in lates release of Celery

hi, is there any documentation on returns value? I have an exit with value 1 with no error message.

(or even starting message)

Hello. I have a problem with Class Task in new celery 4.0.0 and setting task_acks_late = True. If I call a task from a module where celery app is defined - it’s ok. But when I call a task in a different module, it’s always unacked in rabbitmq, even if a task is finished. So it blocks other task to be consumed by worker. I created a short project with an example. https://github.com/kaluha92/celery_test Celery app is defined i

$ celery worker -A project:app --autoscale=8,1 -l info

$ echo $?

1

Also in app/__init__.py I register a task using an import_module to avoid circular imports. I run a task from main.py. And it remains unacked even after a task is finished. In celery 3.1.2 it works fine with the same code(just setting's name changed from task_acks_late to CELERY_TASK_LATE)

Crovax31_: what's in the logs?

malinoff: which logs? nothing in the command outputs

Crovax31_: try -l debug

malinoff: same

malinoff: but when I use wrong project settings, it crashes as expected.

malinoff: Could you help me?

malinoff: this problem happen with celery 4.0 and my project used to works before.

Crovax31_: pastebin your project/app.py please

litwisha: you're likely to have naming issues. http://docs.celeryproject.org/en/latest/usergui...

malinoff: As you can see(https://github.com/kaluha92/celery_test/blo..., I explicitly name my task.

malinoff: I have already read that section, and cannot find that issue in my code. Could you point me to it?

litwisha: you have to instantiate TestCeleryTask when registering

https://github.com/kaluha92/celery_test/blob/ma... here

malinoff: it does not help

litwisha: I have no idea then

malinoff: the funyn part of this issue is that this code is working on 3.1.2

yeah, lots of things have been changed in 4 (that's why it's a major release)

(and it doesn't have to be fully backwards-compatible)

malinoff: it is not a problem with backwards-compatible. It's a problem that I do not know how to make it work in Celery 4

litwisha: why do you need to have that class-based task instead of just a function in the first place?

malinoff: I disabled last django app I added, (with a cron rule) I suppose it should display an issue if it's a setting problem, my app file is ok.

malinoff: bacause it is a sample code. The real code is really huge and it's better and easier to fix this issue than rewrite class-based to function-based tasks :)

I'll try to identify what cause the invisible crash

Crovax31_: I have no idea what are you talking about

litwisha: no, I mean, have you tried to follow "the best practice" from there? http://docs.celeryproject.org/en/latest/whatsne...

malinoff: I added a django app missing __init__.py which didn't bothered django to run but bothered celery…

hope it could have an error message ^^

Crovax31_: still no idea. Have you read my very first message to you?

malinoff: about the project/app.py pastebin? the logs? I fixed without changing the app.py file.

(the logs were none)

I use celery with django, the issue was one of my django app didn't had __init__.py I suppose the celery tasks detection didn't liked it but django didn't care.

(to me django should care so it may be a django issue to not crash)