Repository navigation
build: export impact facts in the background once the graph is queryable - #1848
Merged
Merged
Conversation
…yable Co-authored-by: axiomcode-bot[bot] <334110751+axiomcode-bot[bot]@users.noreply.github.com>
swapnilpaliwal-sd
requested review from
JaredHLZhang,
Whua689 and
suyashpaliwal26
as code owners
October 1, 2026 22:21
swapnilpaliwal-sd
enabled auto-merge
October 1, 2026 22:21
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
1 participant
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.
indexwaited for the warm step (the export of impact facts) after the graph was already queryable. On a large Java repository that was about 3 minutes of looking frozen. The export now runs detached, after it closes the build-lock descriptor so the lock is released when the build ends. Its writes were already atomic renames. A query that arrives first exports the facts itself, as it would without warm.Measured on a repository with 8,619 Java files:
indexreturned at 5 min 21 s (was 7 min 19 s), and the graph is queryable at the same point as before. Tests pass: latency, freshness, refresh, refresh_races, front_door, enrich_budget, and the Java cases (329 of 329).