| 24 Sep 2025 |
 Robbie Buxton | Do you have a minimum repro or is it literally failing on import | 21:22:22 |
 apyh | like, calling torch.compile() fails | 21:22:49 |
| apyh | sec | 21:22:50 |
| Robbie Buxton | Maybe we should start a private chat to avoid spamming | 21:23:17 |
 SomeoneSerge (back on matrix) | I presume it's the -bin version of tensorflow, which means it's patchelfed to use whatever versions of things we've got and inshallah it happens to work? | 22:43:11 |
| SomeoneSerge (back on matrix) | Didn't we recently change triton so it doesn't retain the reference to gcc? | 22:44:50 |
| SomeoneSerge (back on matrix) | all of this should be patched out, maybe it slipped back in during updates | 22:46:17 |
| Robbie Buxton | In reply to @ss:someonex.net
Didn't we recently change triton so it doesn't retain the reference to gcc? This is a different flow that goes via _inductor/config.py, I’ll put the pr in tomorrow once torch finishes building | 22:47:41 |
| 25 Sep 2025 |
 Winter | this is python3Packages.tensorflow | 14:51:03 |
| Winter | but it appears that the _pywrap_... it's looking at is different because I have some stuff in LDLIBRARYPATH lol | 14:51:42 |
| Winter | but it appears that the _pywrap_... it's looking at is different because I have some stuff in LD_LIBRARY_PATH lol | 14:51:49 |
| Winter | i should dig into it at some point | 14:52:06 |
| Winter | out of curiosity/insanity? | 14:52:13 |
| Winter | * out of curiosity/insanity? (both?) | 14:52:23 |
 connor (burnt/out) (UTC-8) | To clarify, are you building PyTorch and Triton with Nix and producing a container, or is this something else? I’d also like to see a reproducer of you have one handy | 15:07:20 |
| connor (burnt/out) (UTC-8) | here be the path to (more) madness | 15:08:12 |
| apyh | In reply to @connorbaker:matrix.org
To clarify, are you building PyTorch and Triton with Nix and producing a container, or is this something else? I’d also like to see a reproducer of you have one handy I'm building a container that includes PyTorch as a runtime dependency, and that PyTorch code calls torch.compile. Let me try to create a minimal repro :) | 15:30:19 |
| apyh | https://github.com/arilotter/nix-torch-compile
a minimal repro ! | 16:31:15 |
| apyh | this includes both things needed to run torch.compile inside a docker container | 16:31:30 |
 hexa (UTC+1) | flox stable nixpkgs is still stuck on aug 27th https://github.com/flox/nixpkgs | 16:50:13 |
| hexa (UTC+1) | not sure who can effectively poke them | 16:50:23 |
| Robbie Buxton | @apyh pr is here https://github.com/NixOS/nixpkgs/pull/446105 | 17:36:25 |
| SomeoneSerge (back on matrix) | Yes, I'm really embarrassed to say, but python3Packages.tensorflow has been defaulting to tensorlfow-bin for about a year now... and from what I've heard, even that is a PITA during upgrades | 23:30:50 |
| SomeoneSerge (back on matrix) | Soooo turns out flox-stable has nothing to do with nixos-stable | 23:31:25 |
| hexa (UTC+1) | so what do they build for nixos-stable then? | 23:32:29 |
| SomeoneSerge (back on matrix) | It's a tad confusing, but uhh they follow nixos-unstable, and when it passes the tests, they merge it into flox/staging, and when that passes more tests that's merged into flox/stable 🙃 | 23:32:45 |
| hexa (UTC+1) | so no relationship to release-25.05 whatsoever | 23:33:03 |
| hexa (UTC+1) | so stable users are fckd | 23:33:13 |
| SomeoneSerge (back on matrix) | I asked them about building the release channels, didn't get a positive reaction yet | 23:33:26 |
| SomeoneSerge (back on matrix) | I'll go ping one more time | 23:33:47 |
