| 14 Oct 2025 |
Mic92 | https://www.phoronix.com/news/Fedora-Nix-Dir-Approved | 21:08:35 |
| 15 Oct 2025 |
fzakaria | oh | 00:28:16 |
fzakaria | wow | 00:28:16 |
fzakaria | is there a way to make this more comprehnsible why it happens
[1/0/1 copied (176.7/176.7 MiB), 29.1 MiB DL] fetching source from https://cache.nixos.org
| 00:30:23 |
fzakaria | I would be down to work on that.. | 00:49:13 |
Mic92 | What do you mean? | 06:25:52 |
Mic92 | In reply to @justinrestivo:matrix.org Hello! Any chance there's a spec about the different Fields provided for each ActivityType in the nix logger? Right now to answer this question I'm grepping the nix codebase for each ActivityType and looking at the arguments to the Activity::Activity constructor to infer the field types and number (if any exist). I'm wondering if there's an easier/more canonical way to do this. I don't think so. There is maybe nix-output-monitor. I think also https://github.com/Thymis-io/thymis had a parser somewhere | 06:32:47 |
maralorn | justinrestivo: This might help. https://github.com/maralorn/nix-output-monitor/blob/main/lib/NOM/Parser/JSON.hs | 07:44:59 |
maralorn | Though note that the nom parser trys to be the union of the codes that nix, lix and determinate nix emit. | 07:45:41 |
fzakaria | Like can it say "Git cache is out of date" or "Tarball expires" or w/e is causing the fetching source. | 13:18:00 |
fzakaria | * Like can it say "Git cache is out of date" or "Tarball expires" or w/e is causing the fetching source.
(I'm thinking it's a flake input fetch although it writes "source fetch") | 13:18:49 |
Robert Hensing (roberth) | Sergei Zimmerman (xokdvium): wdyt? https://github.com/libgit2/libgit2/compare/main...roberth:libgit2:refs-shorthand-multi-segment?expand=1 | 16:00:58 |
Sergei Zimmerman (xokdvium) | In reply to @roberthensing:matrix.org Sergei Zimmerman (xokdvium): wdyt? https://github.com/libgit2/libgit2/compare/main...roberth:libgit2:refs-shorthand-multi-segment?expand=1 Hmm, I was thinking that maybe for our use-case we could also just use is_valid_branch_name in conjunction with is_valid_reference_name instead of the whole normalization dance? Though yeah, this does seem like an oversight in libgit2 as well | 16:33:40 |
Robert Hensing (roberth) | I guess I could open that PR as an alternative if those two functions don't work out? | 16:35:03 |
Sergei Zimmerman (xokdvium) | In reply to @roberthensing:matrix.org I guess I could open that PR as an alternative if those two functions don't work out? Let’s see how upstream reacts. They’be been ignoring my DEL patch for quite some time now | 16:37:13 |
Sergei Zimmerman (xokdvium) | In reply to @roberthensing:matrix.org I guess I could open that PR as an alternative if those two functions don't work out? * Let’s see how upstream reacts. They’ve been ignoring my DEL patch for quite some time now | 16:37:29 |
fzakaria | I'm on a machine with 120 cores and i'm surprised how low parallelism meson compile -j 100 is on it | 17:50:39 |
fzakaria | * I'm on a machine with 120 cores and i'm surprised how low parallelism meson compile -j 100 is on it for compiling Nix | 17:50:46 |
Sergei Zimmerman (xokdvium) | In reply to @fzakaria:one.ems.host I'm on a machine with 120 cores and i'm surprised how low parallelism meson compile -j 100 is on it for compiling Nix PCH make for a pretty bad fork-join | 17:52:38 |
Sergei Zimmerman (xokdvium) | Also the linker | 17:52:56 |
fzakaria | Also, my clangd fails to find the boost header only dependencies? Is there a setting someone can recommend here | 17:52:57 |
fzakaria | I can see they are missing from meson compile as they are not "true" dependencies.. | 17:53:12 |
Sergei Zimmerman (xokdvium) | In reply to @xokdvium:matrix.org Also the linker You should disable b_lto | 17:53:23 |
Philip Taron (UTC-8) | At $WORK we use clang modules to escape the PCH trap | 17:53:25 |
Sergei Zimmerman (xokdvium) | Honestly PCH is pretty good for us. LTO on the other hand is very slow | 17:54:04 |
fzakaria | I think it's cause NIX_CFLAGS is implicit outside meson? | 17:54:06 |
Sergei Zimmerman (xokdvium) | In reply to @philiptaron:matrix.org At $WORK we use clang modules to escape the PCH trap Let’s just wait until 2036 for modules to get supported on all platforms and in meson | 17:55:41 |
Philip Taron (UTC-8) | Our impl doesn't give two hoots about gcc -- it's clang + C23 all the way ;-) | 17:56:20 |
Philip Taron (UTC-8) | Modules (the clang impl) works great with C. | 17:56:39 |
Philip Taron (UTC-8) | Maybe even better than with C++. | 17:56:50 |