Repository navigation
fix: preserve opaque input repositories when loading metadata - #25
Merged
Merged
Conversation
mattnworb
marked this pull request as ready for review
October 1, 2026 19:13
honnix
approved these changes
Oct 1, 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.
Summary
PR #19 introduced
--opaque-input-repositoryand its hashing behavior. The pre-existingLoadIncompleteMetadatacontext copy was not updated to carryOpaqueInputRepositories, so the option was lost before either query backend constructedTargetHashCache.Copy
OpaqueInputRepositoriesinto the temporary context so full hashing and incremental recomputation honor the configured repositories.