New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chord awaited even if not explicitly requested #8995
Comments
This line
If you call chord object |
Thanks for the prompt feedback! I was expecting the group part of it running asynchronously as if been called by |
Checklist
main
branch of Celery.contribution guide
on reporting bugs.
for similar or identical bug reports.
for existing proposed fixes.
to find out if the bug was already fixed in the main branch.
in this issue (If there are none, check this box anyway).
Mandatory Debugging Information
celery -A proj report
in the issue.(if you are not able to do this, then at least specify the Celery
version affected).
main
branch of Celery.pip freeze
in the issue.to reproduce this bug.
Optional Debugging Information
and/or implementation.
result backend.
broker and/or result backend.
ETA/Countdown & rate limits disabled.
and/or upgrading Celery and its dependencies.
Related Issues and Possible Duplicates
Related Issues
Possible Duplicates
Behavior
My goal is to launch a chord from a FastAPI call, which creates N different Tasks to be executed, then not waiting for it to complete, just returning Response 200. To do so I first used the following notation:
Unfortunately it resulted in exploding FastAPI process and no return since chord completion, not desired. So I used this other notation hoping for a different ending:
But still, same behavior happening: FastAPI process exploding and nothing returned.
It's not very clear to me how chord should be used and if they can actually be used asynchronously or not. Maybe there's some specific behavior not properly described in their documentation.
The text was updated successfully, but these errors were encountered: