| 20 Jan 2026 |
 Rutile (rootile) | https://gerrit.lix.systems/c/lix/+/4676
still looking for review | 13:05:25 |
| 22 Jan 2026 |
|  Lotte (it/its)/Cinny (she/her) ΞΈΞ& changed their profile picture. | 16:47:44 |
| 23 Jan 2026 |
|  @io:meat.computer left the room. | 00:53:04 |
|  vczf changed their profile picture. | 18:47:03 |
 Ramses π΅πΈ | nix path-info shows this confusing label ultimate, and I had to go look in the source code to figure out that it basically means that the store path was built locally. Could we not indicate that by locally-built or something like that to make it a lot more obvious? | 19:56:03 |
| Ramses π΅πΈ | * `nix path-info --sigs` shows this confusing label `ultimate`, and I had to go look in the source code to figure out that it basically means that the store path was built locally. Could we not indicate that by `locally-built` or something like that to make it a lot more obvious? | 19:56:50 |
| Ramses π΅πΈ | I could make the CL, but I wanted to check first whether it's a change that would get accepted | 19:59:12 |
| 24 Jan 2026 |
|  holly [she/it] π³οΈββ§οΈ changed their profile picture. | 09:08:06 |
 m | Hello! Is GItHub the only way to login to the Forgejo instance? No email login or Codeberg account? | 12:54:37 |
 K900 | You can set up a Keycloak account with Github, then unlink it | 14:10:03 |
| K900 | Or we can set one up for you manually if you give me an email | 14:10:18 |
| m | Nah, it's alright, don't want to bother. Thank you tho π | 15:16:13 |
| 25 Jan 2026 |
|  dadada changed their profile picture. | 20:34:16 |
| dadada changed their profile picture. | 20:39:16 |
| dadada changed their profile picture. | 21:17:53 |
| 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 |
