Binary cache - improve error message when trying to copy partial closure #2958
Conversation
This file contains 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
|
I marked this as stale due to inactivity. → More info |
|
I closed this issue due to inactivity. → More info |
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.
Since 0207272#diff-4fb7d3254df1c8894c7014adc990dfa1 copying a partial closure isn't allowed, but the error message is a bit misleading: "the reference is not valid" might mean that there's something wrong on the local store (missing path, invalid signature, ...).
Just out of curiosity, why isn't it possible to partially copy a closure to a binary cache? Shouldn't nix be able to pull a closure from different substituters? Isn't this a bit at odd with the
nix copy --no-recursiveoption?