-
Notifications
You must be signed in to change notification settings - Fork 247
Add IOG nix cache in flake configuration #1579
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
Conversation
bors try |
tryTimed out. |
The issue here is that interactive user confirmation of using IOG cache currently stuck the CI … solutions could be to:
|
bors try |
It looks like this has broken one of the old build kite tests that was actually using the flake. It now asks for input from user. |
bors try- |
I could add the same local
|
From https://nixos.org/manual/nix/unstable/command-ref/new-cli/nix3-flake.html#flake-format > `nixConfig`: a set of `nix.conf` options to be set when evaluating any part of a flake. In the interests of security, only a small set of whitelisted options (currently `bash-prompt`, `bash-prompt-prefix`, `bash-prompt-suffix`, and `flake-registry`) are allowed to be set without confirmation so long as `accept-flake-config` is not set in the global configuration.
f6bd524
to
dc2fb4d
Compare
bors try |
bors try- |
bors try |
1 similar comment
bors try |
tryAlready running a review |
bors try- |
bors try |
bors try |
tryAlready running a review |
bors try- |
bors try |
bors try- |
1 similar comment
bors try- |
bors try |
Oh it started #1601. |
tryBuild succeeded: |
These were broken by #1579 because `nix flake lock` now asks for confirmation that it is ok to use the nix configuration in the flake.
These were broken by #1579 because `nix flake lock` now asks for confirmation that it is ok to use the nix configuration in the flake.
From https://nixos.org/manual/nix/unstable/command-ref/new-cli/nix3-flake.html#flake-format