| 18 Dec 2025 |
 ma27 | maybe it was just a debig statement to get output that I dodn't removed and passed through review? | 17:28:28 |
 Rutile (Commentator2.0) feel free to ping | https://gerrit.lix.systems/c/lix/+/4790
the complaining about TMPDIR not being set and tarball.sh failing have an end! | 17:49:37 |
| Rutile (Commentator2.0) feel free to ping | * https://gerrit.lix.systems/c/lix/+/4790
the days of complaining about TMPDIR not being set and tarball.sh failing have an end! | 17:49:45 |
| Rutile (Commentator2.0) feel free to ping | https://buildkite.com/lix-project/lix/builds/7143/steps/canvas?jid=019b329a-3fa3-4367-a2bd-8eb464bed0fd
uhhh what? | 18:28:12 |
| 19 Dec 2025 |
 kloenk | wonder right now if it would make sense to add default values to the get*Attr functions (lix/libfetchers/attrs.hh). Could use that for the tarball striproot CL right now | 19:15:14 |
| Rutile (Commentator2.0) feel free to ping | https://gerrit.lix.systems/c/lix/+/4790
can we get a review | 20:18:21 |
|  Bakbukdibbuk joined the room. | 21:28:11 |
| 20 Dec 2025 |
| kloenk | ah I blind (*noticed maybeGetBoolAttr) | 09:23:37 |
 helle (just a stray cat girl) | I wonder if we should be aliassing it as fetchArchive but that is a further thing, it has for years supported more than just tarballs | 11:42:28 |
| helle (just a stray cat girl) | but erm open wondering, for ux sensibility and doc logic | 11:43:08 |
| helle (just a stray cat girl) | like, this would be an alias, just because fetchTarball applied to an ISO feels like utter nonsense | 14:52:14 |
| kloenk | reading the lix-doc code right now out of interest. First this is technically 3 as _:3 is valid (according to the repl). But also huh funny, if I name the input it gets parsed as an invalid url (e.g. a:a or also a:3) | 22:30:53 |
| 21 Dec 2025 |
| ma27 | is something off with Lix CI currently?
Getting regularlyt errors like
error: failed to read compressed data (truncated input)
and
error: interrupted by the user
| 13:34:28 |
 raitobezarius | Which architecture? | 13:36:17 |
| ma27 | https://buildkite.com/lix-project/lix/builds/7175#019b4088-c1f5-417f-825a-a95537ac1d99 (darwin)
https://buildkite.com/lix-project/lix/builds/7175#019b4088-c22a-4aca-805f-0ca14d68a79c (probably x86_64-linux?) | 13:37:01 |
| raitobezarius | Thanks, we definitely need to investigate this | 13:39:11 |
| raitobezarius | It's not reproducible yet I assume? | 13:39:22 |
| raitobezarius | It would be nice if we can catch it outside the CI | 13:39:32 |
 just1602 | Darwin ci is supposed to be disable from a recent CL, tho | 13:40:33 |
 jade_ | if that's true, I am highly displeased about it | 13:43:59 |
| raitobezarius | I think this is meant to be a temporary disable due to the F2 migration having a subset of the tests not being executed and therefore not passing on Darwin for the time being | 13:47:35 |
| raitobezarius | More information about this ongoing situation is available on the Zulip | 13:47:56 |
| ma27 | I had both in subsequent pushes fwiw. | 13:58:46 |
| raitobezarius | I will be above the arctic circle in the next hours but I will see what I can do in early Monday, thanks | 14:01:58 |
| helle (just a stray cat girl) | If my packing and things keep up I may have a look as well | 14:03:39 |
| 16 May 2024 |
|  zrsk joined the room. | 13:54:49 |
 samrose | In reply to @lunaphied:lunaphied.me
I think there were a few CLs on the Gerrit but nothing being actively worked The other thing that I could do if it helps is test things and try to find bugs. I did do some C++ work in the past, but may lack the time to do it justice here at least for about 30 days or so | 15:55:29 |
 Qyriad | we are not in any rush 🙂 | 17:20:53 |
| samrose | Would it help to also test out the existing Lix code and try to find issues/bugs etc? | 17:23:21 |
| Qyriad | absolutely | 17:23:41 |
