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
When building with Op::BuildDerivation, the derivation is never written to the store. But the drvPath from the client is still available. It gets passed to pre-build-hook as first argument. So the hook ends up with a path to a nonexistent file, and no way to get information about the derivation.
Steps To Reproduce
Expected behavior
I would expect the content of the .drv file to be always available to the pre-build-hook. In this case writing the .drv to a temporary location, or to the store. I think it is not a problem to write it to the store.
Alternatively, if this is deemed unsafe, document the issue in pre-build-hook.
Describe the bug
When building with Op::BuildDerivation, the derivation is never written to the store. But the drvPath from the client is still available. It gets passed to pre-build-hook as first argument. So the hook ends up with a path to a nonexistent file, and no way to get information about the derivation.
Steps To Reproduce
Expected behavior
I would expect the content of the .drv file to be always available to the pre-build-hook. In this case writing the .drv to a temporary location, or to the store. I think it is not a problem to write it to the store.
Alternatively, if this is deemed unsafe, document the issue in pre-build-hook.
nix-env --version
outputAdditional context
NixOS/nixpkgs#256230 (comment)
Priorities
Add 👍 to issues you find important.
The text was updated successfully, but these errors were encountered: