| 19 Dec 2025 |
 hexa | which might be a reference to something else | 02:54:06 |
 zsuper | regarding this, my plan is to create a raw secret option as well as a secretFile option (where the latter takes precedence), just to keep options open for users. But I'll use a regular str for both to avoid secret paths getting copied to the store. | 02:57:58 |
| hexa | the raw secret string option is a bad idea | 02:58:32 |
| zsuper | but it's fine if used with sopsnix right? | 02:58:59 |
| hexa | they pass files | 02:59:24 |
| hexa | not strings | 02:59:25 |
| zsuper | i have not yet setup/learned how sopsnix works, so I am unsure tbh | 02:59:31 |
| hexa | agenix/sopsnix encrypt and pass files | 02:59:42 |
| zsuper | i see, okay thanks | 02:59:57 |
| zsuper | then ill re-evaluate how i go about this. but thanks for the advice regardless! | 03:00:17 |
|  班泽 💕 joined the room. | 08:08:40 |
| 班泽 💕 left the room. | 08:25:17 |
| zsuper | okay, i've been working on the PR for the nixos/bore module, but I'm at a bit of a roadblock when it comes to nixos tests. Since bore local requires a connection to a remote proxy server (i.e. "bore.pub"), should the nixos tests really be connecting to it to verify functionality? Rather, how does networking work with the test suite? Or should I only run tests for the server variant, which simply needs to check if it can listen on 0.0.0.0:<specified port>? | 20:59:24 |
| zsuper | actually i think i might be able to set up a server and a local proxy on the same machine that just interact with each other | 21:14:52 |
| 20 Dec 2025 |
| zsuper | if anyone has free time, could you skim over this PR and see if things look fine? https://github.com/NixOS/nixpkgs/pull/472353
I'm hoping to ask some non-reviewers before I post in the Nixpkgs Review Requests, just so I can minimize the number of cycles I approach reviewers, who might be busy. Thanks in advance! | 02:39:01 |
| zsuper | * if anyone has free time, could you skim over this PR and see if things look fine? https://github.com/NixOS/nixpkgs/pull/472353
I'm hoping to ask some non-reviewers before I post in the Nixpkgs Review Requests channel, just so I can minimize the number of cycles I approach reviewers, who might be busy. Thanks in advance! | 02:39:10 |
| 26 Dec 2025 |
|  isabel changed their profile picture. | 11:37:59 |
|  jappie changed their display name from jappie to jappie @ 39c3. | 15:49:41 |
| 27 Dec 2025 |
| jappie changed their display name from jappie @ 39c3 to jasper @ 39c3 ☎️ 62749. | 13:30:50 |
| 30 Dec 2025 |
| jappie changed their display name from jasper @ 39c3 ☎️ 62749 to jasper. | 23:38:40 |
| jappie | 23:40:10 |
| 4 Jan 2026 |
|  SyBearly joined the room. | 09:32:00 |
| jappie changed their display name from jasper to jappie. | 10:59:43 |
| 5 Jan 2026 |
|  user262728 joined the room. | 03:21:02 |
| 11 Jan 2026 |
|  ivan joined the room. | 01:46:23 |
|  sammy (It/Its) left the room. | 14:37:00 |
| 12 Jan 2026 |
|  Arcterus joined the room. | 09:25:24 |
|  weriomat joined the room. | 09:25:57 |
|  bake.monorail joined the room. | 09:59:43 |
| bake.monorail | (continues from #nix-lang:nixos.org )
Matt Sturgeon:
you're asking a module system question, so NixOS Module System is more suitable 🙂
Ah! I didn't know about that channel. Thanks for pointing me here.
Either by shadowing check with submodule ... // { check = ...; } or extending it using lib.types.addCheck
Mh, I'd need to check how that works before I can fully understand that. Any reading material you suggest? Maybe there's a guide about internals of the modules type system.
Note that these may not work well with v2 check&merge (where checking is partly handled by the merge.v2 function).
No idea what v2 check&merge is, is that opt-in? Is something that's going in soon?
how should an empty module be handled?
None should match, type is a single-element enum with no default, so all of them should fail.
Right now I manually made a "union type" (where everything that a single type would allow, is allowed), and it has already bitten me.
| 10:04:52 |
