Fix date_done timezone issue#8385
Conversation
|
Thank you for the fix! |
|
Ok. We'll fix and add unit tests over the next week. |
|
new tests? |
flake8...................................................................Failed
- hook id: flake8
- exit code: 1
celery/backends/base.py:12:1: F401 'datetime.datetime' imported but unused
celery/backends/base.py:12:1: F401 'datetime.timezone' imported but unused |
|
Also please notice "This branch cannot be rebased due to conflicts”. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8385 +/- ##
=======================================
Coverage 78.05% 78.05%
=======================================
Files 150 150
Lines 18791 18791
Branches 3213 3213
=======================================
+ Hits 14667 14668 +1
Misses 3821 3821
+ Partials 303 302 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
I'm sorry for the late update. |
|
The tests are still failing. |
Co-authored-by: Christian Clauss <[email protected]>
This PR fixes #4842 with my best friend @CodeSik.
celery_taskmeta.date_donewas being saved viautcnow(), but we suggest changing it toapp.now()to apply the value set inapp.conf.timezone.