Lix Development | 413 Members | |
| (Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel. | 137 Servers |
| Sender | Message | Time |
|---|---|---|
| 9 Oct 2025 | ||
* in fact, nixpkgs should just set the NIX_CONFIG abort-on-warn thing assuming it is matched between cppnix and lix, imo | 20:37:56 | |
| I would appreciate this being fixed in nixpkgs' test suite before we can release this feature into GA | 20:38:24 | |
| * I would appreciate this being fixed in nixpkgs' test suite before we can release this feature into GA, because it means that it avoids a period of nixpkgs CI not working properly. | 20:38:47 | |
| I'm in the channel in part because I was grossed out by the code in Nixpkgs. | 21:02:24 | |
| The code we're talking about is this function, right? | 21:08:07 | |
That codepath is only lit up for Lix, since every supported cppnix has builtins.warn. | 21:08:45 | |
| 22:24:02 | ||
right, but the stuff that uses it is relying on NIX_ABORT_ON_WARN=true doing something at all, which it will not do if we implement the lix side well | 23:26:52 | |
* right, but the stuff that uses it is relying on NIX_ABORT_ON_WARN=true doing something at all, which it will not do if we implement the lix side the way we want | 23:27:01 | |
| thus the users of builtins.warn inside nixpkgs test driver code need to start setting NIX_CONFIG so that they don't require us to implement the legacy environment variable | 23:27:31 | |
* right, but the stuff that uses it is relying on NIX_ABORT_ON_WARN=true doing something at all, which it will not do if we implement the lix side the way we want. cppnix reads NIX_ABORT_ON_WARN like the nixpkgs polyfill | 23:27:55 | |
| https://github.com/NixOS/nixpkgs/blob/086b8fb31f8cbab212aa093fd4aa672970ff3212/pkgs/top-level/nixpkgs-basic-release-checks.nix#L49 https://github.com/NixOS/nixpkgs/blob/086b8fb31f8cbab212aa093fd4aa672970ff3212/nixos/modules/misc/documentation.nix#L136 https://github.com/NixOS/nixpkgs/blob/086b8fb31f8cbab212aa093fd4aa672970ff3212/lib/tests/modules.sh#L478 these three need to stop doing this | 23:29:39 | |
| * https://github.com/NixOS/nixpkgs/blob/086b8fb31f8cbab212aa093fd4aa672970ff3212/pkgs/top-level/nixpkgs-basic-release-checks.nix#L49 these three need start doing | 23:29:55 | |
| 10 Oct 2025 | ||
| 07:36:24 | ||
| Rutile (Commentator2.0) feel free to ping: FYI, horrors might be bisecting the whole F2 situation | 10:43:35 | |
| The timeouts are clearly due to F2 hanging and not exiting | 10:45:43 | |
| Why is not clear yet to me | 10:45:47 | |
| (Additional macOS capacity is being connected today as well) | 10:45:58 | |
In reply to @raitobezarius:matrix.orgMe neither | 10:46:01 | |
| We will see what we can do, please be careful with the spurious +1 caused by timeouts of macOS builds | 10:46:19 | |
| Fortunately, F1 → F2 migration doesn't touch any "user level code" | 10:46:32 | |
| But any other change is suffering from this | 10:46:39 | |
In reply to @raitobezarius:matrix.orgYeah | 10:46:52 | |
| (the only big change for that is Pascal strings tbh) | 10:46:57 | |
| * (the only big change for that are Pascal strings tbh) | 10:47:01 | |
In reply to @commentator2.0:elia.gardenCould we check if a revert on this might fix things? | 10:47:15 | |
| passed on the message to horrors | 10:57:20 | |
| 11:23:40 | |
| please give me control groups on macos | 11:23:44 | |
| please | 11:23:45 | |