-
Notifications
You must be signed in to change notification settings - Fork 30
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
Store v2 reports in GCS instead of Redis #960
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #960 +/- ##
==========================================
- Coverage 96.25% 96.25% -0.01%
==========================================
Files 826 826
Lines 19048 19041 -7
==========================================
- Hits 18334 18327 -7
Misses 714 714
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. 📢 Thoughts on this report? Let us know! |
❌ 2 Tests Failed:
View the top 2 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
53e4286
to
09b0993
Compare
This PR includes changes to |
Test Failures Detected: Due to failing tests, we cannot provide coverage reports at this time. ❌ Failed Test Results:Completed 2658 tests with View the full list of failed testspytest
|
09b0993
to
38d2647
Compare
Worker has some dedicated code to move an uploaded report from Redis over to GCS. Instead of having that code, we can just store the report into GCS in the first place. Additionally, this PR also cleans up the `services.archive`, replacing it fully with the `shared.api_archive.archive`. It also forwards all the task arguments directly to the `Upload` task, in addition to storing it in Redis, to be forward compatible to some more planned upload processing improvements.
38d2647
to
782fb8a
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.
in future PRs could you put the actual logical changes in their own commit(s) so they're easier to find/review?
does worker already know that the uploads may no longer be in redis? or does that PR still need to be written
it doesn't look like the newer endpoint saves the report to redis in the first place
# FIXME(swatinem): this is using the `default_path` even for the shelter path, | ||
# how does that even work? shouldn't this be the same as the `path`? | ||
# or is shelter rather making sure that the `upload_params` | ||
# `storage_path` and `url` are set appropriately? |
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.
do we need to answer this Q before merging?
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.
Working on getting an answer in https://sentry.slack.com/archives/C04NC9NNPEG/p1730968157331319?thread_ts=1730814495.218099&cid=C04NC9NNPEG
I believe when using shelter, it ignores the generated upload_url
in favor of returning the storage_path
back to the user which is then both user for the upload on the user end, as well as the read on the worker end.
Yes, I will try :-) One thing kind of led to the other, and I ended up just completely remove the duplicated
Yes, the worker has backwards compatibility code for:
|
Worker has some dedicated code to move an uploaded report from Redis over to GCS. Instead of having that code, we can just store the report into GCS in the first place.
Additionally, this PR also cleans up the
services.archive
, replacing it fully with theshared.api_archive.archive
.It also forwards all the task arguments directly to the
Upload
task, in addition to storing it in Redis, to be forward compatible to some more planned upload processing improvements.Depends on codecov/shared#415