Repository navigation
Expose tracking results in the Collection API - #1281
Merged
Merged
Conversation
clementbiron
approved these changes
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements the second part of RFC #1241: Collection API endpoints serving the tracking results recorded since #1275.
GET /tracking-results: tracking status of all terms, filterable bystatusGET /tracking-result/{serviceId}: tracking status of the terms of a serviceGET /tracking-result/{serviceId}/{termsType}: tracking status of some termsGET /tracking-results/run: summary of the latest completed runLists are paginated like
/versions.Every request reads a single commit, the one that completed the latest run, so a run in progress or crashed never exposes half-updated results. Files are read from Git objects in a single
git cat-file --batchcall for the whole collection, and cached per commit, as the content at a commit never changes.The API opens the repository read-only, as it does for versions and snapshots since #1273: it never touches the working tree, the index or the commit-graph, never takes the writer lock, and never runs the crash recovery, which only the tracker may do. Until a first run completes, the endpoints answer an empty list or a 404. They are not exposed when tracking-results is disabled.