-
Notifications
You must be signed in to change notification settings - Fork 10
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
Make ReportService
sync
#660
Conversation
Codecov ReportAttention: Patch coverage is ✅ All tests successful. No failed tests found.
@@ Coverage Diff @@
## main #660 +/- ##
==========================================
- Coverage 98.06% 97.93% -0.13%
==========================================
Files 437 437
Lines 36892 36864 -28
==========================================
- Hits 36179 36104 -75
- Misses 713 760 +47
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found.
@@ Coverage Diff @@
## main #660 +/- ##
==========================================
- Coverage 98.06% 97.93% -0.13%
==========================================
Files 437 437
Lines 36892 36864 -28
==========================================
- Hits 36179 36104 -75
- Misses 713 760 +47
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. @@ Coverage Diff @@
## main #660 +/- ##
==========================================
- Coverage 98.06% 97.93% -0.13%
==========================================
Files 437 437
Lines 36892 36864 -28
==========================================
- Hits 36179 36104 -75
- Misses 713 760 +47
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Codecov ReportAttention: Patch coverage is
Changes have been made to critical files, which contain lines commonly executed in production. Learn more ✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## main #660 +/- ##
==========================================
- Coverage 98.11% 97.98% -0.13%
==========================================
Files 476 476
Lines 38213 38185 -28
==========================================
- Hits 37492 37417 -75
- Misses 721 768 +47
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 2 files with indirect coverage changes
|
ReportService.initialize_and_save_report
syncReportService
sync
d8b1b1d
to
18985e0
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.
nice, thank you for the cleanup! you are right that sync is preferred. i got rid of a lot of the async
s in #304 in a semi-automated fashion but didn't get em all
everything used to be labeled async
, but the django ORM (which we have begun slowly converging on, away from sqlalchemy) hates that and as you observed all our work is synchronous so we never had anything to yield to
It looks like historically there is a mix of sync/async code. The consensus(?) seems to favor sync code as celery is fundamentally sync. Async code also does not play as well with profiling, which will not show the async code directly in a flamegraph, instead just inserting a `wait` for the async code running in a different thread.
18985e0
to
67e5adc
Compare
It looks like historically there is a mix of sync/async code.
The consensus(?) seems to favor sync code as celery is fundamentally sync.
Async code also does not play as well with profiling, which will not show the async code directly in a flamegraph, instead just inserting a
wait
for the async code running in a different thread.