| 1 May 2025 |
 connor (he/him) | It's also newer than the open kernel modules then? | 23:29:42 |
 Kevin Mittman (EOY sleep) | Experiencing technical difficulties | 23:30:00 |
| 2 May 2025 |
 luke-skywalker | is there a way to pick up on the nvidia-container-toolkit-tools directory containing the runtimes at build time? for example /nix/store/72bp8mb7zzpjifcwasj5wh45ixasmck7-nvidia-container-toolkit-1.17.6-tools | 10:36:29 |
 SomeoneSerge (back on matrix) | getOutput at eval time | 13:25:02 |
| 4 May 2025 |
| luke-skywalker | Interesting. Damn working through the nixOS Manual is still on my bucket list. | 10:27:03 |
| luke-skywalker | took me a a few looks but
"${getOutput "tools" pkgs.nvidia-container-toolkit}"
is actually pretty straight forward.
| 20:05:52 |
| luke-skywalker | šthx a lot | 20:06:01 |
| 5 May 2025 |
 GaƩtan Lepage | Hi there,
I'm working on bumping pytorch to 2.7.0. They now require libcufile.so. Are you aware of this library? Is it already available in nixpkgs? | 12:26:45 |
| GaƩtan Lepage | -> cudaPackages.libcufile FTW. | 12:35:28 |
| 6 May 2025 |
| connor (he/him) | https://github.com/NixOS/nixpkgs/pull/385960 is finally ready for review
I am so tired of writing tests | 00:48:54 |
| connor (he/him) | :L
looks like OpenCV 4.11 doesn't build with CUDA 12.9 due to changes in libnpp https://gist.github.com/ConnorBaker/f258bfa80c82f92c34850482117fa00f | 03:44:18 |
| connor (he/him) | SomeoneSerge (UTC+U[-12,12]): would you mind reviewing / merging https://github.com/NixOS/nixpkgs/pull/404686?
Wanted to get file moves out of the way since setup hook changes will cause rebuilds | 17:00:31 |
| 7 May 2025 |
| SomeoneSerge (back on matrix) | connor (he/him) (UTC-7): RE: manifest data observability
I'll be pushing stuff here as I extend the schema https://cuda-index.someonex.net/sidx/CudaComponent
| 11:26:34 |
| connor (he/him) | God thatās so cool | 13:05:35 |
| connor (he/him) | SomeoneSerge (UTC+U[-12,12]): I've got another one for you https://github.com/NixOS/nixpkgs/pull/404973 | 16:41:25 |
| connor (he/him) | As an added benefit, one could float out imports so that only happens once per nixpkgs instantiation | 16:42:23 |
| SomeoneSerge (back on matrix) | If you're not using aderall idk what you're using xD | 16:57:02 |
| SomeoneSerge (back on matrix) | So fast | 16:57:06 |
| connor (he/him) | Well, that one's sorta broken at the moment because cuda-library-samples doesn't mark derivations as broken if they rely on something unavailable in the current version of the package set | 17:12:37 |
| connor (he/him) | I mean yeah for attention so I can survive my commute; the CUDA stuff is mostly because I think about it every waking moment. (Although I also usually have nightmares about it, too...) | 17:51:11 |
| connor (he/him) | Okay, should be good to go assuming CI passes | 18:24:37 |
| connor (he/him) | To recap, if anyone has spare cycles to review:
- https://github.com/NixOS/nixpkgs/pull/385960 -- very large, lots of bash, but lots of unit tests
- https://github.com/NixOS/nixpkgs/pull/404686 -- very small, no rebuilds
- https://github.com/NixOS/nixpkgs/pull/404973 -- ~900 line diff, no rebuilds outside of CUDA packages, largely just re-organizing to minimize the diff when landing setup hook changes
The setup hook changes (working on a PR) will need all three merged.
| 18:28:26 |
| SomeoneSerge (back on matrix) | Let's start by merging packagesFromDirectoryRecursive | 18:39:44 |
| SomeoneSerge (back on matrix) | Hmm can't we somehow adopt ci/eval and .github/workflows/eval.yml to evaluate, say, release-cuda.nix for PRs labeled "cuda" | 18:47:10 |
| SomeoneSerge (back on matrix) | (with builds and substitutions disabled) | 18:47:28 |
| SomeoneSerge (back on matrix) | connor (he/him) (UTC-7): feel like scratching an itch... git mv pkgs/development/cuda{-modules,} | 19:02:48 |
| connor (he/him) | I kept cuda-modules just because it seems everything else in development follows that naming scheme, but no real reason to keep it that way, I suppose | 19:38:14 |
| SomeoneSerge (back on matrix) |
everything else in development follows that naming scheme
No idea why, but whatever
| 19:39:25 |
| SomeoneSerge (back on matrix) | connor (he/him) (UTC-7): your shims are basically fixups for manifests aren't they? | 20:03:39 |
| connor (he/him) | Yep! | 20:04:17 |
