-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Expose builtins.fetchFinalTree to the user #14634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
We don't care if the user (or more likely the lock file) specifies an incorrect value for revCount, since it doesn't matter for security (unlikely content hashes like narHash).
Same as revCount.
builtins.fetchTree was setting `shallow = true` when fetching from git. That's bad because it makes it behave inconsistently from non-fetchTree fetches, e.g. when updating an input. Instead, the Git fetcher now will do a shallow fetch automatically if `revCount` is already set (e.g. when fetching a lock). Fixes #14588.
This fixes the issue where updating a Git input does a non-shallow fetch, and then a subsequent eval does a shallow refetch because the revCount is already known. Now the subsequent eval will use the repo used in the first fetch.
This may be more efficient than fetchTree since it allows substitution from binary caches if `narHash` is specified in the input attributes. This is what call-flake.nix already used internally.
| Like `fetchTree`, but does not return any additional fetcher attributes (like `revCount`). | ||
| This allows inputs to be substituted if `narHash` is specified. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it only return a path?
|
An alternative is DeterminateSystems#297, which makes |
Motivation
This may be more efficient than
fetchTreesince it allows substitution from binary caches ifnarHashis specified in the input attributes. This is whatcall-flake.nixalready used internally.Depends on #14633.
Corresponding PR to flake-compat: NixOS/flake-compat#79
Context
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.