NixOS Module System | 149 Members | |
| 30 Servers |
| Sender | Message | Time |
|---|---|---|
| 3 Jan 2025 | ||
| Following up on my message about contracts from a while ago, I finally had the motivation and time to create a pre-RFC about it :) https://discourse.nixos.org/t/pre-rfc-decouple-services-using-structured-typing/58257 | 23:19:16 | |
| * Following up on my message about contracts from a little while ago, I finally had the motivation and time to create a pre-RFC about it :) https://discourse.nixos.org/t/pre-rfc-decouple-services-using-structured-typing/58257 | 23:19:47 | |
| 6 Jan 2025 | ||
| Thank you, while I have some objections about some of the details, I do appreciate a lot the effort in making this possible. I tried to provide a short explanations of my concerns on discord. | 11:58:49 | |
| * Thank you, while I have some objections about some of the details, I do appreciate a lot the effort in making this possible. I tried to provide a short explanations of my concerns on discourse. | 11:59:20 | |
| 11 Jan 2025 | ||
| 04:07:52 | ||
| 04:42:56 | ||
| 21:20:48 | ||
| 15 Jan 2025 | ||
| 19:01:46 | ||
| I was just writing some assertions, and wanted to show the option defs for an attr-of an option, isolated using However, I came up with a proof of concept that seems to mostly work, however it's failing My question: is there an intended way to print definitions/locations for an attr-of-an-option and, if not, how could I improve my patch to make it PR-ready? Or is there an alternative approach I could take? In this specific scenario, I'm wanting to | 21:37:21 | |
| 17 Jan 2025 | ||
| 04:39:17 | ||
| 27 Jan 2025 | ||
| 02:49:44 | ||
| 30 Jan 2025 | ||
| 03:01:40 | ||
| 03:02:55 | ||
| 08:55:51 | ||
| 31 Jan 2025 | ||
| 05:06:12 | ||
| 19:35:24 | ||
| Just stumbled into this today:
Is there any reason for this? Why isn't the option just being merged? | 20:12:35 | |
| * Just stumbled into this today:
Is there any reason for this? | 20:15:05 | |
| * Just stumbled into this today:
Is there any reason for this? Why must it be read-only? | 20:17:18 | |
Where does the nodes.server option set come from? I can't see it on the NixOS option search | 20:23:22 | |
| Ah my bad, it's in a NixOS VM test. | 20:26:15 | |
| * Ah sorry for the confusion, it's in a NixOS VM test. | 20:26:28 | |
| It looks like so:
| 20:29:06 | |
| * It looks like so:
| 20:29:17 | |
| 3 Feb 2025 | ||
| 08:53:22 | ||
| This sounds wrong on 3 aspects: 1. it is not supposed to be unique. 2. it is not supposed to be read-only. 3. It cannot be unique and read-only. https://github.com/NixOS/nixpkgs/blob/2dda8c252f59deeba5ef662a7bfc055e43639a55/nixos/lib/testing/nodes.nix#L129-L138 | 10:32:02 | |
| https://github.com/NixOS/nixpkgs/blob/2dda8c252f59deeba5ef662a7bfc055e43639a55/nixos/modules/misc/nixpkgs/read-only.nix#L38 | 10:33:13 | |
| 13:41:17 | ||
| 6 Feb 2025 | ||
| 09:01:01 | ||
| 17:51:18 | ||