| 30 Jan 2026 |
|  Lotte (it/its)/Cinny (she/her) θΔ& changed their profile picture. | 07:54:02 |
|  lillecarl changed their profile picture. | 22:28:10 |
| 31 Jan 2026 |
|  hexchen (migrating to @hexchen:railwit.ch) changed their display name from hexchen to hexchen (migrating to @hexchen:railwit.ch). | 13:31:33 |
|  hexchen joined the room. | 15:40:30 |
| 4 Feb 2026 |
|  tiferrei changed their profile picture. | 03:03:56 |
| tiferrei left the room. | 14:31:25 |
| 7 Feb 2026 |
 raitobezarius (DECT: 7248) | @channel Maintenance window announcements for Lix CI: https://zulip.lix.systems/#narrow/channel/7-Infra/topic/RFC.3A.20merging.20Lix.20Buildkite.20into.20AFNix.20Buildkite/near/6157
TLDR: expect some changes deployed today at midnight CEST, more changes deployed tomorrow at 11:30 CEST.
User impact: short downtime of minutes causing failure or waiting states in the CI. | 18:48:42 |
|  Lisanna joined the room. | 19:50:06 |
| Lisanna | Just dropping a note that I've had to add a note to my project's README explaining that it's not possible to set nix.settings.build-hook on NixOS when using Lix. The release notes deprecating the setting (which causes nix.conf validation to fail) said "if this does affect you, we'd like to hear from you!", so yeah, just letting you know! My project is still very new, and there are no confirmed users of it, but there are several people considering using it.The project is https://github.com/lisanna-dettwyler/nix-scheduler-hook | 19:56:11 |
| raitobezarius (DECT: 7248) | Yep, we have been following your project, super interesting | 20:04:47 |
| raitobezarius (DECT: 7248) | But we would like to make it possible via proper RPC wires than taking over the entire build-hook :D | 20:05:07 |
| raitobezarius (DECT: 7248) | (we being the Lix core team) | 20:05:50 |
| Lisanna | How are you envisioning that working? Will there be a different nix.conf setting for hooks that speak the RPC protocol? | 20:06:35 |
| raitobezarius (DECT: 7248) | If you are familiar with how Snix works, we would fission the whole build subsystem into its own RPC boundary, so someone could tap into a library to spawn a build RPC component and bring their own scheduler logic | 20:07:18 |
| raitobezarius (DECT: 7248) | It's already kinda possible to do something akin that by proxying Nix daemon protocol | 20:07:34 |
| raitobezarius (DECT: 7248) | * It's already kinda possible to do something akin to that by proxying Nix daemon protocol | 20:07:43 |
| raitobezarius (DECT: 7248) | (we would also use that work to enable better out-of-the-box scheduler logic, remote building and more) | 20:08:04 |
| raitobezarius (DECT: 7248) | The remote building hook has been already subject to RPC-ification with Cap'n'Proto, so we are working towards slowly confirming our expectations for this architecture | 20:08:40 |
| Lisanna | I will take a look at the Snix implementation, I have not looked at it at all yet | 20:09:18 |
| raitobezarius (DECT: 7248) | https://snix.dev/docs/components/overview/ | 20:09:29 |
| raitobezarius (DECT: 7248) | They have cute figures | 20:09:31 |
| raitobezarius (DECT: 7248) | https://snix.dev/docs/components/build/protocol/ is relevant too | 20:09:39 |
| Lisanna | ^-^ | 20:09:39 |
| Lisanna | so you would launch your custom builder as a standalone program, and it would then register itself as a builder through a library call? rather than being launched by the Lix cli or daemon directly? | 20:18:19 |
| raitobezarius (DECT: 7248) | the deployment story is not totally hammered down, but a daemon frontend could receive build daemons URIs (remote or local), once you run a lix command that makes use of build, they would be sent to that daemon via RPC | 20:19:19 |
| raitobezarius (DECT: 7248) | but yeah, in that context, Lix CLI or daemon wouldn't execve() a build component | 20:19:52 |
| raitobezarius (DECT: 7248) | it would be delegated | 20:19:55 |
| Lisanna | alright | 20:20:02 |
| Lisanna | I'll keep watch for progress on this front, and see about adding a mode to my program for this kind of usage | 20:21:15 |
| Lisanna | is there an issue tracking it I can follow? | 20:22:28 |
