-
Notifications
You must be signed in to change notification settings - Fork 32
⚗️ Changed periodic_task_result internals in the attempt of solving issue
#7032
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
Conversation
periodic_task_result internals in the attempt of solving issueperiodic_task_result internals in the attempt of solving issue
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7032 +/- ##
==========================================
- Coverage 87.56% 86.76% -0.80%
==========================================
Files 1629 1299 -330
Lines 63454 55099 -8355
Branches 2047 1010 -1037
==========================================
- Hits 55566 47809 -7757
+ Misses 7552 7096 -456
+ Partials 336 194 -142
Continue to review full report in Codecov by Sentry.
|
sanderegg
left a comment
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.
ok
|



What do these changes do?
Somehow after the
periodic_task_resultis done polling for the status it recovers the result and then raises an error error relative to the status retrieval done in the coroutine awaited byawait_for.This implementation is equivalent and tries to avoid the issue by making the situation impossible to occur.
Related issue/s
How to test
Dev-ops checklist