| 4 Dec 2025 |
 raitobezarius | Not impossible but we fight hard to avoid this | 15:26:10 |
 boop-north | Well, anything in the bug tracker that causes such thing lately? | 15:26:37 |
| raitobezarius | I cannot remember something of the sort, you'd need to provide more details about what you are seeing | 15:28:16 |
| boop-north | well, parsec does compile and open | 15:29:34 |
| boop-north | inside the app gui it complains ab libjpeg8 not being there | 15:29:52 |
| boop-north | the nix flake has it in dependencies though | 15:30:02 |
| boop-north | and my system also has it | 15:30:07 |
| boop-north | it doesnt see it as installed | 15:30:17 |
| boop-north | actually im outdated on lix | 15:36:20 |
| boop-north | im having issues updating though | 15:36:29 |
| boop-north | uninstalling 'lix-2.92.0'
error: opening lock file '/nix/var/nix/profiles/default.lock': Permission denied
error: program '/nix/store/1vks5s6rhfardqvzzzc1ca43jfh31bsi-lix-2.94.0/bin/nix-env' failed with exit code 1 | 15:36:35 |
 aloisw | Well they supposedly have a really great test suite, but there are also so many configuration options that it seems impossible to test all interactions between them. | 16:12:17 |
|  Paws changed their profile picture. | 15:58:01 |
| aloisw | getting the spew to stop is very simple: just patch out the print statement | 16:13:20 |
| aloisw | Unfortunately I can't seem to reproduce the spew (obviously without the patch alluded to above, which has in fact not been written) any more, so it's really hard to debug this :( | 16:14:48 |
|  isabel changed their profile picture. | 16:42:02 |
 rosssmyth | They make money by vendoring their customers' test suite into SQLite's test suite to "guarantee" that they do not break. So most configurations that are actually used should be covered. | 16:49:02 |
| rosssmyth | Which is why it is impossible to view or replicate their full test suite | 16:49:50 |
 toonn | Huh, that's an interesting approach to monetizing open source. | 16:51:09 |
| rosssmyth | They also do normal support & NRE stuff | 16:51:45 |
| raitobezarius | In reply to @aloisw:julia0815.de
Unfortunately I can't seem to reproduce the spew (obviously without the patch alluded to above, which has in fact not been written) any more, so it's really hard to debug this :( I think I can provide you with an example | 16:53:15 |
| aloisw | If that example is "run nix-eval-jobs on nixpkgs", then that's not much help. It's also where I have seen it in the past but now I got zero of them. | 16:55:14 |
| raitobezarius | In reply to @aloisw:julia0815.de
If that example is "run nix-eval-jobs on nixpkgs", then that's not much help. It's also where I have seen it in the past but now I got zero of them. And concurrent n-e-j? | 16:56:08 |
| raitobezarius | But not on nixpkgs was my plan | 16:56:15 |
| raitobezarius | I think if you take a look at the AFNix infra evaluation CI scheme, there's like up to 5 nej on large NixOS systems and it still seems to reproduce there | 16:56:46 |
| aloisw | 4 workers on nixpkgs, which I have determined at some point in the past to get the most throughput. | 16:56:55 |
| raitobezarius | Large closures made of small files should probably hit the thing? | 16:57:05 |
| raitobezarius | In reply to @aloisw:julia0815.de
4 workers on nixpkgs, which I have determined at some point in the past to get the most throughput. But that's only one nej instance right? If you do 4 workers * N | 16:57:21 |
| aloisw | Yeah maybe contention is more with 4N workers which should roughly have the same effect. | 16:58:35 |
| aloisw | --store /tmp/teststore shit that might have done it… | 16:59:19 |
