| 26 Dec 2024 |
|  @trofi:matrix.org joined the room. | 15:50:27 |
| @trofi:matrix.org | Please have a look at https://github.com/NixOS/nixpkgs/pull/368366 . I have no idea what I am doing. | 15:50:46 |
 connor (burnt/out) (UTC-8) | Oh my god builtins.sort requires strict total orderings? | 16:28:17 |
| @trofi:matrix.org | No, it requires strict weak ordering, but >= does not provide it. a >= b can't act as lessThat. b < a can, or !(b >= a) can as well. | 16:31:28 |
 SomeoneSerge (back on matrix) | Read your blog post. You got a talent for discovering this stuff before anyone else | 18:57:22 |
| @trofi:matrix.org | If it makes you feel a bit better cuda is not alone in getting sort a bit wrong:
- https://github.com/NixOS/nixpkgs/pull/368429
- https://github.com/NixOS/nixpkgs/pull/368433
| 23:14:25 |
| 27 Dec 2024 |
| connor (burnt/out) (UTC-8) | Trofi would you ping Valentin on the issue? Feels like it’d be good to have this requirement stated in the docs | 01:08:02 |
| 28 Dec 2024 |
| connor (burnt/out) (UTC-8) | ugh thinking about software making me sad
Samuel Ainsworth did you ever find some sort of serenity with CUDA and Nixpkgs? | 00:43:26 |
| connor (burnt/out) (UTC-8) | I'm having thoughts about https://github.com/connorbaker/cuda-packages.
In particular, does it make sense to include CUDA stuff in Nixpkgs proper when we can't take advantage of anything but eval checks?
Would nix-community be a better home?
Just having a growing sense of dread about updating and trying to maintain fast-moving libraries in an environment where stuff can (or does) break constantly and there's no notification of such breakage (except maybe by the community Hydra instance?).
There's also the understanding that in Nixpkgs, everything work together simultaneously.
As an example, I'd hate to try to upgrade OpenCV (or PyTorch) so it works with newer versions of CUDA, only to find out it causes some gnarly Darwin/ROCm/non-CUDA issue.
Thinking out-of-tree designs would afford us the ability to break stuff, though that comes with a number of drawbacks (duplicating nix expressions for packages and having slight variations, merging in upstream changes, etc.).
Maybe this is just fatigue talking; I think a number of these complaints were raised in a discourse post Sam made a few years ago. | 00:54:19 |
| connor (burnt/out) (UTC-8) | I mean, I certainly want to upstream the library functions and additional setup hooks/logging functionality I wrote because they're (in my opinion) widely useful.
Just... the CUDA stuff. | 00:55:26 |
| connor (burnt/out) (UTC-8) | * I'm having thoughts about https://github.com/connorbaker/cuda-packages. In particular, does it make sense to include CUDA stuff in Nixpkgs proper when we can't take advantage of anything but eval checks? Would nix-community be a better home? Just having a growing sense of dread about updating and trying to maintain fast-moving libraries in an environment where stuff can (or does) break constantly and there's no notification of such breakage (except maybe by the community Hydra instance?). There's also the understanding that in Nixpkgs, everything work together simultaneously. As an example, I'd hate to try to upgrade OpenCV (or PyTorch) so it works with newer versions of CUDA, only to find out it causes some gnarly Darwin/ROCm/non-CUDA issue. Thinking out-of-tree designs would afford us the ability to break stuff, though that comes with a number of drawbacks (duplicating nix expressions for packages and having slight variations, merging in upstream changes, etc.). Maybe this is just fatigue talking; I think a number of these complaints were raised in a discourse post Samuel made a few years ago. | 12:33:14 |
 lromor | Is anyone at chaos congress? | 16:16:44 |
| @trofi:matrix.org | Good idea! Done as https://github.com/NixOS/nix/issues/12106#issuecomment-2564375843 | 16:36:40 |
|  matthewcroughan changed their display name from matthewcroughan to matthewcroughan (DECT: 56490). | 18:41:55 |
| 29 Dec 2024 |
| lromor set a profile picture. | 16:13:20 |
| connor (burnt/out) (UTC-8) | Just tried to build PyTorch and I completely forgot it vendors its dependencies, was stunned to see it building ONNX | 21:49:20 |
| SomeoneSerge (back on matrix) | I wish... matthewcroughan (DECT: 56490) maybe? | 21:50:20 |
