| 29 Dec 2025 |
 Alexandros Liarokapis | Would probably also work for mesa on nix standalone systems as well | 00:19:29 |
| Alexandros Liarokapis | One could probably directly reuse the discovery functionality of the nvidia container toolkit go library | 00:29:52 |
| Alexandros Liarokapis | * One could probably directly reuse the discovery functionality of the nvidia container toolkit go library (or flatboat or similar) | 00:49:05 |
| Alexandros Liarokapis | * One could probably directly reuse the discovery functionality of the nvidia container toolkit go library (or flatpak or similar) | 00:49:13 |
 Gaétan Lepage | Hi!
I finally found some time to work on the llama-cpp-python-libcuda.so-stubs-missing bug and fixed outlines by skipping its pythonImportsCheckHook and tests when cudaSupport was enabled.
This allowed me to finally unblock the vllm bump.
It builds fine with and without cudaSupport. Feel free to test/review: https://github.com/NixOS/nixpkgs/pull/467418 | 17:36:41 |
 connor (burnt/out) (UTC-8) | Good post about the exact problem we run into when trying to create dynamic libraries for Magma with our default set of CUDA capabilities: https://fzakaria.com/2025/12/28/huge-binaries | 18:06:21 |
| connor (burnt/out) (UTC-8) | I won't be in the weekly call tomorrow btw | 18:06:33 |
| 30 Dec 2025 |
 Collin Arnett | Hello, I'm working on getting a nixos module written for dcgm. connor (burnt/out) (UTC-8) I know you have an old draft PR so I'm basing a lot of it on that. As part of that I've had to go ahead and update dcgm and it's prometheus exporter. I would appreciate it if I could get a review from anyone here if they have the chance :) https://github.com/NixOS/nixpkgs/pull/474721 . dcgm is kind of a cursed package so I did my best with the patching but if anyone has any critical feedback it would be more than welcome. | 14:49:19 |
| connor (burnt/out) (UTC-8) | I don’t personally use it and will have limited time so I don’t think I can review it, but I’m fine with anyone else reviewing and merging it | 18:08:38 |
| 31 Dec 2025 |
 lon | Wow super cool, thank you. Haven't run benchmarks but it looks a lot faster | 13:58:23 |
| Collin Arnett | Oh no worries. As far as the dcgm nix module I was mostly mentioning you above to make sure credit was given where credit is due :D | 16:21:47 |
| 1 Jan 2026 |
|  matthewcroughan changed their display name from matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) to matthewcroughan. | 20:04:02 |
| 5 Jan 2026 |
 Ari Lotter | is there a more general python/ml Nix chat anywhere? trying to get some stuff that isn't technically cuda-related going | 21:24:26 |
| Gaétan Lepage | Just ask it here. There is no other "python+ML" official room I'm aware of.
The closest would be the official Python room, but you would end up pinging even more people. | 21:27:55 |
| Ari Lotter | yeah fair enough.
trying to depend on the python module outlines, it seems not to build because it has a hard requirement of outlines-core==0.2.11, but the version of -core in nixpkgs is 0.2.13. seems like latest outlines release still does depend on 0.2.11. wondering if it makes more sense to PR to.. revert the core update? because it seems like outlines must have been "broken" since https://github.com/NixOS/nixpkgs/commit/a5370c8752db2465791097660563b3b2441b56ac
either that or something changed about the pythonRuntimeDepsCheck - the error i get is that f"{package_name}{requirement.specifier} not satisfied by version {package.version}"
| 21:46:53 |
|  Kevin Mittman (UTC-8) changed their display name from Kevin Mittman (EOY sleep) to Kevin Mittman (UTC-8). | 22:03:14 |
| Ari Lotter | * yeah fair enough.
trying to depend on the python module outlines, it seems not to build because it has a hard requirement of outlines-core==0.2.11, but the version of -core in nixpkgs is 0.2.13. seems like latest outlines release still does depend on 0.2.11. wondering if it makes more sense to PR to.. revert the core update? because it seems like outlines must have been "broken" since https://github.com/NixOS/nixpkgs/commit/a5370c8752db2465791097660563b3b2441b56ac
either that or something changed about the pythonRuntimeDepsCheck - the error i get is that f"{package_name}{requirement.specifier} not satisfied by version {package.version}": outlines-core==0.2.11 not satisfied by version 0.2.13
| 22:39:27 |
| 6 Jan 2026 |
| Gaétan Lepage | Yes, I already fixed it in https://github.com/NixOS/nixpkgs/pull/476381.
You can track it here: https://nixpkgs-tracker.ocfox.me/?pr=476381 | 11:39:15 |
 apyh | everyone is so fast lol thank you | 15:04:29 |
| 8 Jan 2026 |
| Gaétan Lepage | RE onnxruntime-dependent segfaults when cudaSupport is enabled.
Apparently, this does not only happen in onnxscript, but also in rapidocr-onnxruntime. | 10:12:03 |
| Gaétan Lepage | Addressed in https://github.com/NixOS/nixpkgs/pull/478028. | 10:46:28 |
| Gaétan Lepage | connor (burnt/out) (UTC-8) what is your plan for updating the default cudaPackages alias?
Bumping to 12.9 or directly to 13? | 11:02:00 |
| Gaétan Lepage | I ask this because evaluating nixpkgs with cudaSupport = true is currently broken because of python3Packages.paddlepaddle which doesn't have sources for Cuda 12.8. | 12:39:45 |
| Gaétan Lepage | And this broke our cuda-packages-unstable hydra jobset :/ | 12:40:29 |
|  wilhelmines joined the room. | 16:58:46 |
| connor (burnt/out) (UTC-8) | Is that backport-able? | 17:19:30 |
| connor (burnt/out) (UTC-8) | I’d be okay bumping to the latest CUDA once we get OpenCV bumped to the latest release (4.13 came out recently and includes fixes to build with CUDA 13), assuming nothing super important breaks | 17:20:53 |
| connor (burnt/out) (UTC-8) | One of the longer discussions I keep pushing back is deciding on whether or not we want to do release gating, and if so, which packages should be considered blockers. | 17:21:32 |
 SomeoneSerge (back on matrix) | Yes we should, at the least on pytorch | 19:52:18 |
| SomeoneSerge (back on matrix) | Eval error like that is a bug. if you have the time, append "or null" to the attribute look up | 19:56:31 |
