!yxFWYdmeLrdzdoIrcE:maralorn.de

nix-output-monitor

96 Members
https://github.com/maralorn/nix-output-monitor32 Servers

Load older messages


SenderMessageTime
8 Dec 2025
@vodros:matrix.orgVodros joined the room.14:36:16
@vodros:matrix.orgVodrosHi, 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:maralorn.demaralornI will have to look into that.14:43:59
@vodros:matrix.orgVodrosAwesome thanks!14:45:36
@maralorn:maralorn.demaralorn 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:maralorn.demaralornSo potentially I have revert that change before the release.14:47:33
@maralorn:maralorn.demaralorn* So potentially I have to revert that change before I can cut a release.14:47:44
@maralorn:maralorn.demaralornOther 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:maralorn.demaralornSo I probably should just drop that plan.14:49:23
@maralorn:maralorn.demaralornI think a release until end of year sounds realistic.14:50:44
@vodros:matrix.orgVodrosI understand. No pressure then. If reverting is manageable then that would be cool, otherwise we'll just wait ig.14:51:23
@vodros:matrix.orgVodrosYeah that's reasonable14:51:32
@vodros:matrix.orgVodrosAnd above all thanks for your work :)14:52:05
@hexa:lossy.networkhexait doesn't look comfortable either ๐Ÿ˜„ 14:54:37
@hexa:lossy.networkhexa
nix-output-monitor 2.1.8
nix (Lix, like Nix) 2.95.0-pre20251201-dev_2ae7480
14:54:52
@hexa:lossy.networkhexaimage.png
Download image.png
14:55:05
@maralorn:maralorn.demaralornYeah, I know. ๐Ÿ˜„14:55:56
@maralorn:maralorn.demaralornAlthough I have to say that this whole misery started with a behavior change in lix.14:56:20
@hexa:lossy.networkhexaright, but at least lix people are here who offered better signaling, no?14:57:12
@maralorn:maralorn.demaralornYeah, sure.15:06:53
@maralorn:maralorn.demaralornThe problem is I kinda feel that this should be fixed on the nom side.15:07:17
@maralorn:maralorn.demaralornI am just trying to reflecting blame for the problem not yet being fixed.^^15:07:49
@hexa:lossy.networkhexaif the signaling isn't clear and needs to be guessed that is bad15:15:24
@maralorn:maralorn.demaralornSure. But that is a structural problem which wonโ€™t go away for nom unless all nix implementations fix it.15:22:06
@maralorn:maralorn.demaralornYes, I guess for this case specifically we could really do the capabilities approach where lix signals correctly why a job finishes.15:23:36
@maralorn:maralorn.demaralornThen I keep the old detection for everything else and do the better detection for lix.15:23:58
@maralorn:maralorn.demaralornOtoh the fix could be easy when I look at the logs by Emma. But I am actively trying not do that because I donโ€™t have time for this. ๐Ÿ˜„15:25:00
@hexa:lossy.networkhexaone implementation adding better signaling can force another to follow suit ๐Ÿ˜„ 15:25:02
@maralorn:maralorn.demaralornThe last week I developed on nom was super fun, I am really enjoying the result, but the ensuing sleep deprecation triggered a medium mental health crisis. i.e. nom development is a health hazard for me. ๐Ÿ˜„15:26:16
@maralorn:maralorn.demaralorn* The last week I developed on nom was super fun, I am really enjoying the result, but the ensuing sleep deprivation triggered a medium mental health crisis. i.e. nom development is a health hazard for me. ๐Ÿ˜„15:26:26

There are no newer messages yet.


Back to Room ListRoom Version: 9