| 18 Oct 2024 |
 Gaétan Lepage | Idk if an update would help. Unfortunately, they have heavily changed their packaging internals and we are quite stalling on this project... | 20:53:57 |
 mcwitt |
Unfortunately, they have heavily changed their packaging internals and we are quite stalling on this project...
Ah man, sorry to hear. I've been occasionally checking in on the progress of JAX updates (most recently https://github.com/NixOS/nixpkgs/pull/318995), and have to say that it seems like a herculean effort to debug all the build issues that come up with each update, not to mention the frequent breakage of downstream dependencies since things are moving so quickly with JAX. Thanks so much for you work on this! I've benefited a ton from having JAX in nixpkgs.
| 22:21:30 |
| Gaétan Lepage | Glad that it's useful for you ! Sometimes I wonder if there are people using the nix python set ^^.
Indeed, each update involves some work. While most of the time it is pretty straightforward, the recent changes (related to bazel) are much more annoying. | 22:31:53 |
| Gaétan Lepage | hexa (UTC+1) I am indeed unable to build tensordict from my torch 2.5.0 update PR.
I systematically gets stuck at 22%, no matter the core count apparently.
I will try to investigate this tomorrow. | 22:41:37 |
 hexa (UTC+1) | Thank you. | 22:42:09 |
| 19 Oct 2024 |
| Gaétan Lepage | Very weird, I was now able to build it.
It does this in the middle, but the tests are apparently all succesfull. | 11:35:50 |
| Gaétan Lepage | 
Download clipboard.png | 11:35:54 |
| Gaétan Lepage | Sometimes this message doesn't show up and the package builds just fine... | 11:47:44 |
| hexa (UTC+1) | as I said, 6th gen intel breaks, 8th gen intel works | 12:53:32 |
| hexa (UTC+1) | both are essentially skylake | 12:53:40 |
| hexa (UTC+1) | my build farm is 6th gen fwiw | 12:53:45 |
 hacker1024 | In reply to @hexa:lossy.network
reliably crashes and gets stuck on 6th gen intel Could it be out of date microcode? | 12:55:56 |
| hexa (UTC+1) | 🤔 | 12:56:10 |
| hexa (UTC+1) | hardware.cpu.intel.updateMicrocode = lib.mkDefault config.hardware.enableRedistributableFirmware;
| 12:56:44 |
| hexa (UTC+1) | which defaults on config.hardware.enableAllFirmware | 12:57:09 |
| hexa (UTC+1) | which defaults to false | 12:57:19 |
| hexa (UTC+1) | 🤡 | 12:57:20 |
| hacker1024 | Rip | 12:57:24 |
| hexa (UTC+1) | thank you nixos-generate-config | 12:57:34 |
| hacker1024 | No guarantee that it'll fix it but it can't hurt | 12:57:42 |
| hacker1024 | They have long lists of errata | 12:57:52 |
| hexa (UTC+1) | yeah, worth a try | 12:58:00 |
| hexa (UTC+1) | can always roll back | 12:58:03 |
| hexa (UTC+1) | thx | 12:58:58 |
 connor (burnt/out) (UTC-8) | I keep forgetting I added myself as a maintainer to glibc until I get emails for reviews lmao | 19:09:59 |
| connor (burnt/out) (UTC-8) | SomeoneSerge (utc+3) Gaétan Lepage thoughts on having backendStdenv automatically propagate autoAddDriverRunpath and autoPatchelfHook? I feel like forgetting to add the former is a footgun people keep firing, and the latter is a great check to make sure all your dependencies are either present or explicitly ignored. | 19:22:47 |
| Gaétan Lepage | I am not sure to be qualified to answer properly. From my point of view, these kind of automations indeed help and avoid sneaky mistakes. | 19:24:29 |
| hexa (UTC+1) | hacker1024: I think your recommendation was spot on | 21:27:27 |
| hexa (UTC+1) | at 22% I see the first [pt_main_thread] instances | 21:27:36 |
| hexa (UTC+1) | and they don't seem to crash with microcode updates applied | 21:27:50 |
