Skip to content
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

Fix/celery beat #395

Merged
merged 3 commits into from
Sep 6, 2024
Merged

Fix/celery beat #395

merged 3 commits into from
Sep 6, 2024

Conversation

mgdaily
Copy link
Contributor

@mgdaily mgdaily commented Sep 5, 2024

The docs are here https://docs.celeryq.dev/en/stable/reference/celery.apps.beat.html

This was breaking in production as we were using an outdated call to the celery beat binary. Help from this stack overflow comment: https://stackoverflow.com/a/65213590

The docs are here https://docs.celeryq.dev/en/stable/reference/celery.apps.beat.html
This was breaking in production as we were using an outdated call to the celery beat binary. Help from this stack overflow comment: https://stackoverflow.com/a/65213590
Copy link

@jchate6 jchate6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is celery[redis]>5 still correct? Should we limit this at all on the upper end?

No more breaking changes, please.
@mgdaily mgdaily merged commit 6bc7240 into main Sep 6, 2024
6 checks passed
@mgdaily mgdaily deleted the fix/celery-beat branch September 6, 2024 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants