-
Notifications
You must be signed in to change notification settings - Fork 90
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
access counts gql #4202
access counts gql #4202
Conversation
@@ -215,13 +215,24 @@ type User { | |||
type AccessCountForDate { | |||
date: Datetime! | |||
value: Int! | |||
sum: Int! # running sum |
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.
not sure this is required, since it can be easily calculated on the consuming side, but it feels quite convenient to have this
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4202 +/- ##
=======================================
Coverage 37.69% 37.69%
=======================================
Files 768 768
Lines 35317 35317
Branches 5215 5215
=======================================
Hits 13313 13313
Misses 20769 20769
Partials 1235 1235
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
} | ||
|
||
type BucketAccessCounts { | ||
byExt(groups: Int): AccessCountsGroup[] |
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.
don't merge / collapse the groups by default
(maybe we don't have to do that at all, just keep that logic on the front-end, not sure)
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.
I'm not quite sure what you mean
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.
catalog code "collapses" access counts into a finite number of "bands", so if there's too many extensions, less frequent ones are merged into a single "other" band.
this proposed api design assumes there's no such collapsing performed by default (when groups
are null or zero)
@@ -556,6 +567,9 @@ type Query { | |||
searchMorePackages(after: String!, size: Int = 30): PackagesSearchMoreResult! | |||
subscription: SubscriptionState! | |||
|
|||
bucketAccessCounts(bucket: String!, window: Int!): BucketAccessCounts | |||
objectAccessCounts(bucket: String!, key: String!, window: Int!): AccessCounts |
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.
we don't have a proper "bucket" entry point currently, and i don't feel comfortable designing / adding that now, so let's just add separate queries.
tho feel free to add a simple container type to group this if you like
994da13
to
d32fd6f
Compare
I guess this can be closed now |
Description
TODO
optipng
on any new PNGsbuild.py
for new docstrings