-
Notifications
You must be signed in to change notification settings - Fork 8
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
fix: Avoid key-error when inserting asset chunks #550
Conversation
Codecov ReportAttention: Patch coverage is ✅ All tests successful. No failed tests found.
📢 Thoughts on this report? Let us know! |
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## main #550 +/- ##
==========================================
+ Coverage 88.50% 88.53% +0.03%
==========================================
Files 451 451
Lines 13107 13109 +2
Branches 1528 1528
==========================================
+ Hits 11600 11606 +6
+ Misses 1184 1180 -4
Partials 323 323
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
CodSpeed Performance ReportMerging #550 will create unknown performance changesComparing Summary
|
This PR updates some logic when creating associations to filter out assets that we don't have a mapping for when creating our asset_chunks prior to insertion.
Seeing around 40 instances of the error in the last week so not super wide spread but still worth fixing -> https://cloudlogging.app.goo.gl/Ckj7wYDciPS34nBb6
Closes codecov/engineering-team#3187
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.