-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 Usage job not executing successfully #10244
Fix Usage job not executing successfully #10244
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 4.20 #10244 +/- ##
=========================================
Coverage 16.13% 16.14%
- Complexity 12966 12973 +7
=========================================
Files 5639 5639
Lines 494251 494297 +46
Branches 59899 59908 +9
=========================================
+ Hits 79766 79788 +22
- Misses 405664 405684 +20
- Partials 8821 8825 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
code lgtm
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.
LGTM
@winterhazel , can you confirm this is not a problem in older versions? |
#9741 was introduced in 4.20.1 |
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.
LGTM
Thank you for the PR. I'm working on a Usage related PR and this bug is blocking my progression.
I tested the proposed fix in my local environment and the Usage job executed successfully.
Description
The Usage job does not execute successfully in 4.20.1 because
cloud_usage.account
is missing the columnapi_key_access
(introduced in #9741). This PR fixes the issue.Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
How Has This Been Tested?