| 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 |
