-
Notifications
You must be signed in to change notification settings - Fork 7
AVGRATE changes #110
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
AVGRATE changes #110
Conversation
Codecov Report
@@ Coverage Diff @@
## main #110 +/- ##
=========================================
Coverage 22.98% 22.98%
Complexity 75 75
=========================================
Files 65 65
Lines 1679 1679
Branches 52 52
=========================================
Hits 386 386
Misses 1284 1284
Partials 9 9
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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.
This looks like a revert of the core module. I thought we verified that on build, let me go check that..
We don't verify it. Our normal check( which is missing also and I will add) verifies that it's on main, which wouldn't have caught this. I forgot we don't enforce that it doesn't move backwards since that would prevent reverting. |
@sarthak77 there are some conflicts on hypetrace-core-graphql, can you retry updating sub-module? |
This comment has been minimized.
This comment has been minimized.
* feat: add distinct aggregation * add DISTINCT_ARRAY operator * update attribute service
Ref issue : hypertrace/hypertrace#314