| 5 Dec 2025 |
 maralorn | thx! I have saved log and screenshot and will look into it when the rest of my live stops burning. | 11:39:06 |
 Emma [it/its] | 
Download clipboard.png | 13:39:23 |
| Emma [it/its] | that's also an interesting one | 13:39:26 |
| Emma [it/its] | (almost at the 3h mark in this single build run, so there's plenty of logs if you want them) | 13:40:15 |
| 7 Dec 2025 |
 whispers (it/fae) | having download progress is so nice (we'd often stop a long build and manually nix copy it over just for that), thank you so much for implementing that <3 | 18:08:51 |
| 8 Dec 2025 |
|  Vodros joined the room. | 14:36:16 |
| Vodros | Hi, since support for download progress was merged the day after the last release, are there any plans to make a new release soon? | 14:37:48 |
| maralorn | I will have to look into that. | 14:43:59 |
| Vodros | Awesome thanks! | 14:45:36 |
| maralorn | Vodros: The problem is that we currently have kind of an experimental build finished detection on main and I don’t feel comfortable releasing that. | 14:47:16 |
| maralorn | So potentially I have revert that change before the release. | 14:47:33 |
| maralorn | * So potentially I have to revert that change before I can cut a release. | 14:47:44 |
| maralorn | Other problem is that I would love to polish the download progress stuff even more before release. But I probably won’t get to that in a while. | 14:48:39 |
| maralorn | So I probably should just drop that plan. | 14:49:23 |
| maralorn | I think a release until end of year sounds realistic. | 14:50:44 |
| Vodros | I understand. No pressure then. If reverting is manageable then that would be cool, otherwise we'll just wait ig. | 14:51:23 |
| Vodros | Yeah that's reasonable | 14:51:32 |
| Vodros | And above all thanks for your work :) | 14:52:05 |
 hexa | it doesn't look comfortable either 😄 | 14:54:37 |
| hexa | nix-output-monitor 2.1.8
nix (Lix, like Nix) 2.95.0-pre20251201-dev_2ae7480
| 14:54:52 |
| hexa | 
Download image.png | 14:55:05 |
| maralorn | Yeah, I know. 😄 | 14:55:56 |
| maralorn | Although I have to say that this whole misery started with a behavior change in lix. | 14:56:20 |
| hexa | right, but at least lix people are here who offered better signaling, no? | 14:57:12 |
| maralorn | Yeah, sure. | 15:06:53 |
| maralorn | The problem is I kinda feel that this should be fixed on the nom side. | 15:07:17 |
| maralorn | I am just trying to reflecting blame for the problem not yet being fixed.^^ | 15:07:49 |
| hexa | if the signaling isn't clear and needs to be guessed that is bad | 15:15:24 |
| maralorn | Sure. But that is a structural problem which won’t go away for nom unless all nix implementations fix it. | 15:22:06 |
| maralorn | Yes, I guess for this case specifically we could really do the capabilities approach where lix signals correctly why a job finishes. | 15:23:36 |
