feat(gitter): git commit graph and patch ID caching#4728
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Ly-Joey
changed the title
And the start to git enumeration but the graph traversal needs more work
Because it is faster than stdout pipe after some experimentation.
Contributor
|
/gemini review |
We now have: - mutex locking on patch ID related data in repo struct - repo-level rw locking - singleflight on operation-level - request-level concurrency control
Ly-Joey
changed the title
Contributor
Author
|
To keep this PR moving along (and so I don't have to keep rebasing and resolving merge conflicts), I've decided to split the affected commit related logic (mainly graph walking and cherrypick detection) into another branch and a future PR. |
Contributor
Author
|
/gemini review |
This comment was marked as off-topic.
This comment was marked as off-topic.
Contributor
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
another-rex
reviewed
Feb 20, 2026
another-rex
previously approved these changes
Feb 23, 2026
Member
|
Just note if the go importer gets merged first to change the |
tymzd
pushed a commit
to tymzd/osv.dev
that referenced
this pull request
Apr 13, 2026
Building on top of google#4508 & co. Key changes: - Added foundational structures to save commit details to disk - We now parse full git history into in-memory graph for commit traversal - Parallelised patch ID calculation. They are loaded from the cache, meaning subsequent requests to the same repo only need to compute patch IDs for new commits. API updates: - `POST /cache`: Triggers a clone / fetch and store the computed commit details - `/getgit` renamed to `GET /git` - [x] change the endpoint in Python WIP (To be added in follow-up PRs to keep this more manageable to review): - [ ] `POST /affected-commits`: accepts a list of events and returns the list of affected commits - `/affected-commits` should accept a list of ranges as valid request as well - Probably refactor the check last fetch time and refetch logic, because every operation relies on it. - [ ] Check if a repoistory exist (/git-good) - [ ] Resolve refs to commit hash
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
4 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.
Building on top of #4508 & co.
Key changes:
API updates:
POST /cache: Triggers a clone / fetch and store the computed commit details/getgitrenamed toGET /gitWIP (To be added in follow-up PRs to keep this more manageable to review):
POST /affected-commits: accepts a list of events and returns the list of affected commits/affected-commitsshould accept a list of ranges as valid request as well