Docs: figure out how infra pollers handle too many refs |
|||||||
Issue descriptionThe refs in gitiles https://repo/url.git/+refs?format=json will now show all gerrit patches, including closed ones. I am not sure how this scales and whether we have any implicit assumptions that refs endpoint will return mostly bounded number of refs.
,
Aug 3 2016
,
Aug 11 2016
,
Aug 11 2016
I think we'll see this as we migrate V8 and WebRTC :) It's hard to predict this.
,
Sep 27 2016
We should send an email out to infra informing them about potential issues. Also document it within the playbook?
,
Jan 13 2017
Right now, the chromite refs json is >4MB. Chromium/src.git will hit that in a year and keep growing past that. We need the ability to get a subset of the refs. Proposed api: foo.googlesource.com/repo/+refs/heads?format=json only returns refs in the "refs/heads" namespace. foo.googlesource.com/repo/+refs/changes?format=json only returns CL refs Might also be useful to have a paging/continuation token system just for the sake of good design.
,
Mar 27 2017
The ?format=text and ?format=json pages now support filtering refs by path. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by benhenry@chromium.org
, Jun 24 2016