| 28 Jul 2025 |
 emily | yeah | 00:16:24 |
 jade_ | copied directly out of the bazel thing | 00:16:25 |
| jade_ | https://git.lix.systems/lix-project/lix/issues/935 here filed another issue with the intent of the fault being written down | 00:20:28 |
| emily | losing events sounds really bad for build logs | 00:20:59 |
| jade_ | agreed | 00:21:14 |
| emily | especially since a big Hydra farm spends most of its time with builders under intense load | 00:21:19 |
| emily | (well… ideally) | 00:21:24 |
| jade_ | backpressure is probably the correct choice here, but it does mean that theres a correct amount of blocking for logs... | 00:21:38 |
| jade_ | just not the amount we have | 00:21:47 |
| jade_ | we also do blocking syscalls on every log line lol | 00:22:09 |
| emily | I think it's already true, absent Nix, that make >/dev/null is faster than make | 00:22:20 |
| emily | IIRC Ninja might do smart stuff to mitigate that | 00:22:29 |
| jade_ | plausible | 00:23:02 |
| jade_ | i think ninja also tries to stop process output from getting interleaved too bad | 00:23:12 |
| emily | (might be dependent on it not streaming all build logs to the terminal. but that's at least an available/default mode here, too) | 00:23:16 |
| jade_ | your daily reminder that 50% of the problems in nix are the protocol being an absolutely cooked design :( | 00:23:50 |
 just1602 | The nix idea wasn't bad, but it would have taken another PhD thesis to properly implement the protocol 😅 | 00:24:54 |
 raitobezarius | In reply to @esperlily:matrix.org
oh hey you just merged 3765 as I was reading through it. I was going to ask, why are we still copying the file when we have no chroot? don't we just need to set NIX_SSL_CERT_FILE to point at the caFile in that case? I'm so sorry | 00:28:38 |
| raitobezarius | In reply to @esperlily:matrix.org
oh hey you just merged 3765 as I was reading through it. I was going to ask, why are we still copying the file when we have no chroot? don't we just need to set NIX_SSL_CERT_FILE to point at the caFile in that case? no chroot doesn't mean that there's no sandbox policy applied no? | 00:29:08 |
| jade_ | okay fyi the build jobs are running as Utility (presumably alongside the daemon) | 01:05:05 |
| emily | maybe the QoS needs to be higher then :) | 01:05:33 |
| emily | though user interactive sounds like it would be interesting | 01:05:56 |
| emily | but worth a try at least… | 01:05:58 |
| jade_ | .. whereas if i run them in a terminal via like, ninja to build a normal lix from source, it's Default | 01:06:07 |
| emily | right | 01:06:17 |
| emily | utility is what it's meant to be | 01:06:36 |
| emily | but it does mean sacrificing perf | 01:06:40 |
| emily | user-initiated might be good to try | 01:06:45 |
| jade_ | i am wondering if the nix daemon itself should be at U-Init or Default | 01:08:12 |
| jade_ | because it is likely to be the one causing the blocking | 01:08:24 |
