| 8 Jun 2026 |
 Rutile | did ^^ | 11:14:39 |
| 9 Jun 2026 |
|  Alex0 joined the room. | 09:50:41 |
|  maralorn joined the room. | 11:14:11 |
| maralorn | Is anyone working in the area of the json output format? I am looking for volunteers to do a small extension so that I can reduce the complexity and increase reliability of nom. | 11:16:41 |
 raitobezarius | Can you open an issue and explain what you would like so we can kickstart the conversation with the team? | 11:35:34 |
|  Astreaprtcl joined the room. | 12:02:33 |
| maralorn | Kann someone generate me an account for lix.systems@maralorn.de? Or is it preferred to use github SSO? | 12:34:57 |
 piegames | done. Please try to log in now | 12:38:57 |
|  Lotte (it/its)/Cinny (she/her) θΔ& changed their profile picture. | 13:24:21 |
| 10 Jun 2026 |
| Astreaprtcl | the CI for https://gerrit.lix.systems/c/lix/+/5646 seems to be stuck with broken pipe could someone please try to restart the jobs? | 05:44:23 |
| Rutile | done ^^ | 07:55:08 |
| Astreaprtcl | ty :3 | 07:55:19 |
| 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 |
| samrose |
- how do people feel about the existing test suite that comes along with nix source code or Lix?
| 17:23:48 |
| Qyriad | it's pitiful | 17:24:10 |
| samrose | heh | 17:24:16 |
| raitobezarius | expanding it is cool | 17:24:23 |
| raitobezarius | writing new tests for builtins which are not tested | 17:24:30 |
| raitobezarius | new test behaviors, etc. | 17:24:32 |
| Qyriad | we have three flavors of test:
gtest (offer only available in libexpr and libutil) bash script virtual machine
the vast, vast majority of testing is in the "bash script" flavor and it is a mess | 17:25:01 |
| samrose | I was just going to ask on the "functional" tests: do we still like using bash there? | 17:25:56 |
| samrose | the last time that I worked on a major nix related cli project that used bash, or bats for testing, over time it became rather kind of hard to maintain | 17:26:42 |
| samrose | I am not usually a big python fan, but in that project we heard from some in the Rust community that they actually use Python to test CLI and seem to have success there. | 17:27:59 |
| Qyriad | no gods please kill bash testing. the problem is that it's kind of really difficult to migrate an entire test suite and be sure that you actually migrated the test suite correctly and won't lose coverage accidentally in the process, which makes any kind of migration a bit nerve wracking | 17:28:36 |
| samrose | yes it's a rather large undertaking | 17:28:52 |
| samrose | could be done in chunks | 17:28:59 |
