| 17 Aug 2025 |
 helle (just a stray cat girl) | no use maintaining f1 if we have this sort of breakage | 12:30:55 |
 niko ⚡️ | Sure, I'll try. Also the other failure is from bumping sqlite or one of its dependencies it seems like | 12:33:21 |
| niko ⚡️ | Overriding sqlite from 3.50.2 to 3.50.1 resolved the other two failures | 12:33:54 |
| niko ⚡️ | Which is kinda scary because I can't see why it'd be sqlite at fault | 12:34:49 |
| niko ⚡️ | Someone more knowledgable and with more time than me should look into this I have no clue if it's a genuine regression or yet another false-negative because of auto-allocate-uids | 12:49:17 |
| niko ⚡️ | * Someone more knowledgeable and with more time than me should look into this I have no clue if it's a genuine regression or yet another false-negative because of auto-allocate-uids | 12:49:25 |
| niko ⚡️ | It's not sqlite directly, that's a relief | 12:56:28 |
| niko ⚡️ | Whatever I'm not chasing this I'll just write f2 tests (or attempt to) | 12:56:45 |
 emily | fwiw the Darwin tests pass for me when not under heavy load | 14:02:27 |
| emily | i.e. I suspect some portion flakindss and some portion auto-allocate-uids | 14:02:49 |
| emily | * i.e. I suspect some portion flakiness and some portion auto-allocate-uids | 14:02:57 |
 jade_ | this is hydrasect (which doesn't have a data source anymore) but i have been poking at the channel script authors to make this automatic also | 16:54:30 |
 Rutile (Commentator2.0) feel free to ping | In reply to @helle:tacobelllabs.net
would it be in your skillset to move these to functional2? (this may depend on some f2 features not quite finished) Builds dont quite work on darwin yet, otherwise f2 is feature complete fwiw | 19:19:07 |
| Rutile (Commentator2.0) feel free to ping | Or well, feature parity | 19:19:25 |
| 18 Aug 2025 |
 raitobezarius | In reply to @commentator2.0:elia.garden
Builds dont quite work on darwin yet, otherwise f2 is feature complete fwiw oh very cool to know | 11:09:47 |
| raitobezarius | emily i think i will merge up to https://gerrit.lix.systems/c/lix/+/3850/7 today | 11:10:24 |
| raitobezarius | fwiw | 11:10:24 |
| raitobezarius | so that the stack becomes smaller | 11:10:30 |
| helle (just a stray cat girl) | there are also some small devx things with f2 that may cause some annoyances with writing certain types of tests | 11:11:15 |
| raitobezarius | gerrit merge noises | 13:08:57 |
| jade_ | does anyone know why wrapPythonPrograms = true is on by default? it appears to be Totally Broken because it means that if you ever invoke a python program from a python program, it loses the calling environment | 13:21:31 |
 Winter | fyi https://git.lix.systems/lix-project/lix/commit/858de5f47a1bfd33835ec97794ece339a88490f1 should probably be backported to a release, getting build errors on unstable bc lowdown bump | 13:47:52 |
| emily | uh. I would have preferred not. I still did not finish checking whether the reproducibility issues in my Darwin system closure are solvable and I think I had unpushed changes. | 14:30:48 |
| raitobezarius | argh, how problematic is it in practice? | 14:31:20 |
| raitobezarius | i mean if the reproducibility issues are impossible to resolve, we can still revert things, it's more noise | 14:31:50 |
| raitobezarius | but this is fine | 14:31:52 |
| raitobezarius | for next time, please don't hesitate to put WIP or an unresolved comment to mark that the change is not ready | 14:32:14 |
| raitobezarius | In reply to @winter:catgirl.cloud
fyi https://git.lix.systems/lix-project/lix/commit/858de5f47a1bfd33835ec97794ece339a88490f1 should probably be backported to a release, getting build errors on unstable bc lowdown bump it's backported to all releases but i surmise that we didn't do any further release | 14:33:30 |
| emily | I did, but it looks like I resolved the comment as all-looks-resolvable-in-principle. I did not get around to sending the most basic fixes off to Nixpkgs for review though. I was pipelining testing it with the LLVM 21 bump which has felt more time-critical; if I'd known there was a hurry I could have prioritized but with the author-submits model I was just planning to come back to it once I felt confident and you said you were looking into one of the patches in the stack so I was also waiting on that | 14:48:51 |
| emily | I'm concerned about changing the format/prefix length twice | 14:49:01 |
