-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
nix refetches the global registry json pointlessly for locally overriden flakes #9087
Comments
Particularly inconvenient when debugging a network issue with a tool you know is in the store but you can't use |
FYI this bug is fixed in https://lix.systems because we simply vendored the flake registry. |
It definitely seems sensible to allow pinning the registries list itself, along with the individual pins. |
Actually you can do that today if you want, set The real boon of Lix's strategy is it's fixed by default and so we can honestly call this bug fixed in Lix despite barely changing the code because un-fixing it requires re-enabling the online flake registry fetch functionality that we simultaneously deprecated. |
Perfect! This is 👌 and should absolutely be the default. One fewer round trip! And no network calls at all for packages in the store. Very nice, thank you. |
Describe the bug
This is arguably in some respects the same bug as #7075 but only takes ${timeToCompleteHttpRequest}.
Given the following setup, nix will refetch the global registry when building things from non-fully-qualified flake reference:
Steps To Reproduce
nix run --debug nixpkgs#hello
Expected behavior
Nix should not refetch the registry if it can resolve the flake reference entirely locally.
nix-env --version
output~ » nix-env --version
nix-env (Nix) 2.17.0
Additional context
Priorities
Add 👍 to issues you find important.
The text was updated successfully, but these errors were encountered: