You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
error: access to URI 'github:nix-community/poetry2nix/3c92540611f42d3fb2d0d084a6c694cd6544b609?narHash=sha256-2GOiFTkvs5MtVF65sC78KNVxQSmsxtk0WmV1wJ9V2ck%3D' is forbidden in restricted mode
error: worker error: error:
… in the right operand of the update (//) operator
at /nix/store/sk4ga2wy0b02k7pnzakwq4r3jdknda4g-source/default.nix:137:19:
136| ${key} = (attrs.${key} or { })
137| // (appendSystem key system ret);
Steps To Reproduce
create a flake configuration
do not set nix.settings.restrict-eval
add an input like github:<something>
Expected behavior
Expected not to see errors about restricted eval mode.
Metadata
nix-env (Nix) 2.24.11
Additional context
Up until this point, the same configuration worked fine, but we bumped to unstable and now restrict-eval is throwing errors even though it is unset. We were able to get past this by adding github: gitlab: to allowed-uris, though I'd assume that setting restrict-eval = false would also work. EDIT: restrict-eval = lib.mkForce false; does not fix it, somehow hydra-eval-jobs is still running in restricted mode.
May also be important to note this is on hydra machines.
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
The documentation states that
restrict-eval
innix.conf
is set to false by default: https://hydra.nixos.org/build/292448195/download/1/manual/command-ref/conf-file.html#conf-restrict-eval, however, I'm running into errors that should only happen ifrestrict-eval
is true. The configuration does not haverestrict-eval
set at all...Steps To Reproduce
nix.settings.restrict-eval
github:<something>
Expected behavior
Expected not to see errors about restricted eval mode.
Metadata
nix-env (Nix) 2.24.11
Additional context
Up until this point, the same configuration worked fine, but we bumped to unstable and now
restrict-eval
is throwing errors even though it is unset. We were able to get past this by addinggithub: gitlab:
toallowed-uris
,though I'd assume that setting. EDIT:restrict-eval = false
would also workrestrict-eval = lib.mkForce false;
does not fix it, somehowhydra-eval-jobs
is still running in restricted mode.May also be important to note this is on hydra machines.
Checklist
Add 👍 to issues you find important.
The text was updated successfully, but these errors were encountered: