-
Notifications
You must be signed in to change notification settings - Fork 4
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
Upgrade to Celery 5.0 #17
Upgrade to Celery 5.0 #17
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @king-alexander! I noted some minor changes that I'd like to see included here before I approve.
683c4b9
to
e356a2d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for figuring out how to get us onto the latest major version! I have some housekeeping and version pinning related feedback for you below.
Celery 5.0 introduced breaking changes to the command line interface. One such change is that you can no longer pass "celery" in argv when programatically starting the celery app. This commit updates our invocation and requires Celery 5.0 (Singularity), the lowest stable version we can support with this change.
782a463
to
a5df33e
Compare
Co-authored-by: Nick <[email protected]>
…alexander/admiral into improvement/upgrade-celery
4208f55
to
8d0388f
Compare
The ports in use should be specified as a quoted string to avoid conflicts with YAML Base-60 floating point numbers. Co-authored-by: Nick <[email protected]>
Co-authored-by: dav3r <[email protected]>
Quotation marks around environment variables are preferred to the -/= syntax for consistency with the rest of the file. Co-authored-by: dav3r <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think everything looks good to me now, thank you @king-alexander for sorting all of this out! ⚓
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
…alexander/admiral into improvement/upgrade-celery
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your work on getting this upgrade across the finish line! One small suggestion just to fix a comment's alignment but otherwise LGTM ✔
🗣 Description
Starting with version 5.0, Celery parses command line options with Click, which introduced breaking changes. I updated the call in
celery.py
that starts the app accordingly.I didn't completely avoid scope creep. In the process of upgrading, I noticed a a minor bug when the component services of admiral were starting up. Redis Commander depends upon Redis, but attempted to start first, leading to a recoverable error. This blip was corrected in
docker-compose.yml
.💭 Motivation and context
This change resolves #6.
🧪 Testing
I successfully started admiral in both of its modes:
celery-shell
andbash
. Furthermore, all unit and system tests passed.✅ Pre-approval checklist
to reflect the changes in this PR.
✅ Post-merge checklist