| 13 May 2022 |
 osnyx (he/him) | In reply to @janne.hess:helsinki-systems.de
Hydra doesn't have an option to toggle this for some reason * Ah, that explains why it's on in Hydra | 10:27:47 |
 das_j | ah allowed-uris is the option I was talking about but I have no idea what to do with it. Maybe set it to /nix/store? I really don't know | 10:28:42 |
| osnyx (he/him) | In reply to @linus:schreibt.jetzt
Because restrict-eval doesn't affect fixed-output derivations, which are the mechanism through which sources are usually fetched. That doesn't read like this in the nix docs: https://nixos.org/manual/nix/stable/command-ref/conf-file.html#conf-restrict-eval
So if this is true it should better be mentioned there. | 10:28:48 |
 @linus:schreibt.jetzt | the key word there is "evaluator" | 10:29:21 |
| osnyx (he/him) | I first will have a look how that directory is actually created, I guess some tracing comes in handy there. | 10:29:37 |
| osnyx (he/him) | In reply to @linus:schreibt.jetzt
the key word there is "evaluator" Ah, the component that creates the .drv files to be realised by the nix daemon later? | 10:31:32 |
| @linus:schreibt.jetzt | not necessarily the daemon, but yes | 10:31:44 |
| osnyx (he/him) | Understood. Yeah, not always the daemon (see single-user installs), but I wanted to simplify for clarity. Thx. | 10:32:27 |
| @linus:schreibt.jetzt | the evaluator also talks to the daemon on multi-user installs, in order to actually create the .drvs :) | 10:33:10 |
| osnyx (he/him) | das_j: Do you think a remark about the naming of "is forbidden in restricted mode" (Hydra error, not found in Hyfra docs) vs. "restrict-eval" (underlying Nix feature) deserves its own issue or shall I mention it in PR #888? | 10:34:29 |
| das_j | In reply to @os:matrix.flyingcircus.io
das_j: Do you think a remark about the naming of "is forbidden in restricted mode" (Hydra error, not found in Hyfra docs) vs. "restrict-eval" (underlying Nix feature) deserves its own issue or shall I mention it in PR #888? I don't know, maybe not in #888 since I doubt this will ever get merged or looked at again | 10:35:00 |
| osnyx (he/him) | It could be mentioned in the Hydra docs that the "restricted mode" is derived from "restrict-eval", or the error message could be rephrased | 10:35:40 |
| osnyx (he/him) | Or if #888 is abandoned than someone (I?) might just document that restricted mode == restrict-eval is always switched on. | 10:36:22 |
| das_j | In reply to @os:matrix.flyingcircus.io
Or if #888 is abandoned than someone (I?) might just document that restricted mode == restrict-eval is always switched on. It's not abandoned, we do rebase it to master when needed because it's one of the 20 patches we pick into our downstream hydra :D | 10:37:01 |
| das_j | In reply to @os:matrix.flyingcircus.io
It could be mentioned in the Hydra docs that the "restricted mode" is derived from "restrict-eval", or the error message could be rephrased But what would the error message say? It's not like you can just change an option to fix the issue | 10:37:25 |
| osnyx (he/him) | In reply to @janne.hess:helsinki-systems.de
But what would the error message say? It's not like you can just change an option to fix the issue Huh? I thought that's what #888 is introducing. But I honestly haven't checked where evaluator_restrict_eval comes from. | 10:39:11 |
| das_j | In reply to @os:matrix.flyingcircus.io
Huh? I thought that's what #888 is introducing. But I honestly haven't checked where evaluator_restrict_eval comes from. Yeah that is what it's introducing. But I doubt this will ever get merged so having an error message that says something else isn't really helpful. Documenting that is probably a better way to go (but in a separate PR!) | 10:40:04 |
| osnyx (he/him) | Okay.
Todolistengeräusch | 10:40:45 |
| osnyx (he/him) | In reply to @linus:schreibt.jetzt
how does it get there? Ah, one of the nix paths contained a ${nixpkgs} reference in a path. I replaced that with a relative path (possible in that particular case), but adjusting the NIX_PATH might also be a viable way. | 11:44:31 |
| @linus:schreibt.jetzt | In reply to @os:matrix.flyingcircus.io
Ah, one of the nix paths contained a ${nixpkgs} reference in a path. I replaced that with a relative path (possible in that particular case), but adjusting the NIX_PATH might also be a viable way. If anything you want it to be an input in your hydra jobset definition, because NIX_PATH doesn't apply globally in Hydra | 11:55:16 |
| osnyx (he/him) | I'll have a look, thx. | 11:56:01 |
| 14 May 2022 |
|  Florian | W3F changed their display name from Florian | W3F to Florian | OoO -> 29.5.. | 11:55:50 |
| 15 May 2022 |
|  dadada (they/them) changed their display name from dadada (er/they) to dadada / Tim. | 13:19:12 |
 @ulrikstrid:matrix.org | Some maybe stupid questions:
* How do I make docker/VM images available after a run?
* How can I upload my cache to cachix/S3 after a run? | 14:03:05 |
 cransom | you can use runCommand to push paths to a cache. if you look around for references to hydra-build-products in nixpkgs, you'll see how to create links for downloads in hydra. | 16:49:58 |
| @ulrikstrid:matrix.org | In reply to @casey:hubns.net
you can use runCommand to push paths to a cache. if you look around for references to hydra-build-products in nixpkgs, you'll see how to create links for downloads in hydra. Thank you 🙏 | 16:53:59 |
| 16 May 2022 |
|  @0b11:matrix.org joined the room. | 04:23:39 |
| @0b11:matrix.org changed their display name from 0b01010011 to 0x53. | 04:26:08 |
|  @cgroves:matrix.org left the room. | 13:19:04 |
|  @lina:monero.social left the room. | 18:15:46 |
