fix(deps): update Celery to 5.6.0+ to fix task_id None error#3571
fix(deps): update Celery to 5.6.0+ to fix task_id None error#3571ANJAN672 wants to merge 4 commits into
Conversation
|
marking as waiting behind #3336 |
|
#3336 has merged. This now requires a rebase but should be good to go as soon as that happens |
|
taking this over |
5d3fd4d to
5d54ce7
Compare
|
This docker build failure message is possibly not related to this PR. It suggests something is off. I do not think celery is the default queue name. rror: q-1 | 2026-02-19 03:21:21.918387+00:00 [error] <0.749.0> Channel error on connection <0.741.0> (10.89.0.2:55950 -> 10.89.0.5:5672, vhost: 'augur_vhost', user: 'augur'), channel 1:
Error: q-1 | 2026-02-19 03:21:21.918387+00:00 [error] <0.749.0> operation queue.purge caused a channel exception not_found: no queue 'celery' in vhost 'augur_vhost' |
|
@sgoggins that error is benign. i saw it when messing with the rabbit version and documented it as known benign on the wiki https://github.com/chaoss/augur/wiki |
|
This does have a more serious error though in the docker build Stack Trace |
|
@ANJAN672 are you still interested in helping the maintainers merge this PR? I dont think it can move forward in its current state given the failing CI checks |
Working on it now !! |
Fixes augurlabs#3458 Updates Celery from ~=5.5 to >=5.6.0 to fix a bug where task_id becomes None during exception handling while executing a task chain within a chord. This was reported in celery/celery#9774 and fixed in Celery 5.6.0. Signed-off-by: ANJAN672 <rockyanjan672@gmail.com>
…in docker Signed-off-by: ANJAN672 <rockyanjan672@gmail.com>
Signed-off-by: ANJAN672 <rockyanjan672@gmail.com>
b73af06 to
124c7db
Compare
Signed-off-by: ANJAN672 <rockyanjan672@gmail.com>
f4cf793 to
314ac2f
Compare
|
@MoralCode and @sgoggins , can u please review this! |
Updates Celery from
~=5.5to>=5.6.0to fix a bug wheretask_idbecomesNoneduring exception handling while executing a task chain within a chord.This was reported in celery/celery#9774 and fixed in Celery 5.6.0.
Description
celery~=5.5→celery>=5.6.0in pyproject.tomluv.lock(Celery 5.5.3 → 5.6.2)This PR fixes #3458
Notes for Reviewers
uv.lockupdatedSigned commits