Repository navigation
0.7.11: imported repos stop staying Pending (annotated tags, import refs) - #8
Merged
Merged
Conversation
…ed tags, hidden or deleted import refs) from the ref advertisement, so prepared refs publish; a pending read refreshes an index with outstanding pushes. 0.7.11
This was referenced Oct 15, 2026
This branch was successfully 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.
Root cause (kit 0.7.10 did not fix it). The index publishes a repo's prepared refs only when no recorded push is outstanding (
fragments:pending-refs). A push is acknowledged when the index resolves the ref to the pushed oid. Some pushes can never match:r.peeled ?? r.oid) but pushed as its tag object (gildforge/desktopv0.1.0: tag 8670bac8 → commit 0ae1ffac);import/pr/N) hidden from the index while the import runs, or deleted by the import cleanup outside the push path.So every import with an annotated tag or PRs stayed "Pending · repository data is being prepared". Live D1: 19 of 65
prepared_repository_refsrows arepending=1, including import-probe3/4/5.Fix. When the index reads the ref advertisement, pushes recorded before that read are settled if the ref is advertised at exactly the pushed oid, or is gone (
settleAdvertisedRefs, pure, inengine/repo-refs.ts)._metastill settles only through the index. A pending conversation read now refreshes (instead of just waking) an index with outstanding pushes, so already-stuck repos heal when viewed.Evidence:
npm run typecheck0;npm test23/23, with newsrc/engine/repo-refs.test.ts(annotated tag settled, deleted import ref settled, a ref at another oid and_metastay outstanding).-claude