-
Notifications
You must be signed in to change notification settings - Fork 6
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
Merge 1.19.0 #1341
Merged
Merged
Merge 1.19.0 #1341
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added os upgrade to be sure the libraries as up to date as possible everytime the image is built. - Replaced vim with nano - Used uv instead of pip (super fast drop in replacement) - Compile translatable messages during build - Added proper release scheme attributes - Separated Celery into worker, beat and monitor containers - Added additional health checks to steer the ordering of container-startup There was 1 container reserved for all Celery related things: worker, beat and monitoring. According to Celery documentation it's best to have a separate Beat process so you can scale separately. Also, combining monitoring with the events itself could cause issues. Everything is separated now. Additional health checks and dependancies are introduced to Docker-compose so Celery nicely waits for the database to be prepped.
- The notifications-api-common library interferes with Celery's task loading mechanism, which prevents tasks form our apps from showing up in the admin. The temporary fix is to load the library after all our apps
The Celery docs make clear that the name parameter of the task decorator should be unique and that generally it functions as an identifier the task. From this we can also infer that names that change at runtime, due to gettext, are undesirable. This in fact created issue with triggering certain periodic tasks in the admin, due to a mismatch between the registered name (English) and the translated name used at runtime (Dutch). TLDR: let Celery generate the name, and directly translate the periodic task names for Beat so that the entries in the Django periodic task admin are human-readable. This is not ideal as we would like to use (lazy) gettext here, but Celery doesn't allow that, so this strikes the balance between human-readability and predictable task discovery.
- specifying multiple package versions without separator (comma or semicolon) is deprecated since pip 24.1
Backported Docker and Celery fixes
This addresses several CVEs and fixes a nasty unicode issue that appeared when since Python 3.11.9 and 3.12.3. See: https://docs.djangoproject.com/en/4.2/releases/4.2.12/
* tag 'v1.18.2': Release 1.18.2 ⬆️ Updated Django to 4.2.14 🔖 Release 1.18.1 Fix version specifications for requirements [#2636] stop using human-friendly names for tasks [#dimpact-107] Hotfix for celery search task not showing in admin 🐳 Updated Dockerfile, separated Celery containers 💄 Updated favicon. 🔧 Update nvm version to match the Docker version. 🐛 Define scriptpath for setup_configuration.sh
* tag 'v1.19.0': Release 1.19.0 [#2657] fix incorrect command invocation for failing mail digest task [#2657] migrate send_failed_email_digest cron to Celery Update translations Release 1.18.2 ⬆️ Updated Django to 4.2.14 🔖 Release 1.18.1 Fix version specifications for requirements [#2636] stop using human-friendly names for tasks [#dimpact-107] Hotfix for celery search task not showing in admin 🐳 Updated Dockerfile, separated Celery containers 💄 Updated favicon. 🔧 Update nvm version to match the Docker version. 🐛 Define scriptpath for setup_configuration.sh
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #1341 +/- ##
========================================
Coverage 95.09% 95.09%
========================================
Files 994 994
Lines 36244 36244
========================================
Hits 34468 34468
Misses 1776 1776 ☔ View full report in Codecov by Sentry. |
swrichards
requested review from
alextreme and
pi-sigma
and removed request for
alextreme
August 8, 2024 08:54
pi-sigma
approved these changes
Aug 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.