-
Notifications
You must be signed in to change notification settings - Fork 10
feat: use new CAs with commits failed fixed #443
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
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #443 +/- ##
==========================================
- Coverage 94.17% 94.14% -0.04%
==========================================
Files 1272 1276 +4
Lines 47180 47221 +41
Branches 1507 1509 +2
==========================================
+ Hits 44434 44458 +24
- Misses 2440 2456 +16
- Partials 306 307 +1
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 #443 will not alter performanceComparing Summary
|
Codecov Report❌ Patch coverage is ❌ Your patch status has failed because the patch coverage (79.52%) is below the target coverage (90.00%). You can increase the patch coverage or adjust the target coverage. 📢 Thoughts on this report? Let us know! |
5862c32 to
7aab319
Compare
7aab319 to
5fa23b3
Compare
we create a function to allow to run a timescale index creation with transaction per chunk and modify the django state at the same time we also create functions for removing the retention policy on a CA and create a TTL per row retention policy for a hypertable and for a CA
5fa23b3 to
c0ea1aa
Compare
the "commits failed” field on the CAs previously failed to deduplicate commits that failed across days so if commit A failed yesterday and today it would count for 2 commits failed, the new CAs fix this so we want to consume information from them instead of the old ones. This commit also reorganizes the timescale aggregation code in the GQL API and checks the is_called_from_sentry_app function to decide which version of the aggregation to use
c0ea1aa to
b395f9f
Compare
Issues attributed to commits in this pull requestThis pull request was merged and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
the "commits failed” field on the CAs previously failed to deduplicate
commits that failed across days so if commit A failed yesterday and
today it would count for 2 commits failed, the new CAs fix this so we
want to consume information from them instead of the old ones.
This commit also reorganizes the timescale aggregation code in the GQL
API and checks the is_called_from_sentry_app function to decide which
version of the aggregation to use