Repository navigation
Conversation
Reference counting checks whether each relationship row comes from a dirty or deleted file. Both checks can rediscover the repository and read HEAD, so a kernel-scale survey repeatedly performs the same work. Snapshot the excluded paths and overlay counts together before scanning. Stream the LanceDB batches so the query can consume each batch as it arrives. Exercise both clean and edited worktrees in the reference-count test. Co-authored-by: Chris J Arges <[email protected]>
12458
force-pushed
the
file-survey-reference-counts
branch
from
November 20, 2026 05:04
0f83543 to
f0ea480
Compare
12458
marked this pull request as ready for review
November 20, 2026 05:26
This branch has not been deployed
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
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.
file_surveychecks whether each indexed relationship came from a dirty or deleted file. Both checks can rediscover the Git repository and read HEAD for every row.Benchmarks
0f83543) with its parent onmain(d233043), both release builds with Rust 1.98.1.93f51579, 1,060,300 functions, 1.1 GB), built withmain'ssemcode-index.semcode-mcpstdio server. Each request was afile_surveycall fordrivers/net/wireguard/peer.c. The patched build ran first, so the baseline got the warmer page cache.main, and 1.07 s, 0.71 s, 0.74 s with this PR.main, and 1.01 s, 0.69 s, 0.70 s with this PR. The modification appended a caller ofwg_peer_createandwg_peer_puttodrivers/net/wireguard/device.c. Both builds raised those counts from 1 to 2 and from 21 to 22.functions_definedandtypes_definedmatched the baseline exactly. The three patched responses were identical.Validation
cargo +stable test --locked --offline --quiet(621 passed)cargo +stable fmt --check