!yxFWYdmeLrdzdoIrcE:maralorn.de

nix-output-monitor

94 Members
https://github.com/maralorn/nix-output-monitor31 Servers

Load older messages


SenderMessageTime
21 Nov 2025
@jappie:jappie.devjappie joined the room.17:03:08
@isabel:isabelroses.comisabel changed their profile picture.18:14:39
23 Nov 2025
@d:metropolis.nexusdave :3 set a profile picture.16:52:39
24 Nov 2025
@emma:rory.gayEmma [it/its]i wonder if this is a reasonable way to detect finished builds as fallback?17:20:29
@emma:rory.gayEmma [it/its]clipboard.png
Download clipboard.png
17:20:29
@emma:rory.gayEmma [it/its]because i'd assume that nix builds dont start running until all of their inputs are finished?17:20:53
@maralorn:maralorn.demaralornIs this on nom main?17:23:18
@emma:rory.gayEmma [it/its]thats on my server, so no17:23:34
@maralorn:maralorn.demaralornAh, okay. Then this is probably already fixed.17:23:50
@emma:rory.gayEmma [it/its]ah17:23:55
@maralorn:maralorn.demaralornI mean it’s not perfect on main, but definitely different.17:24:15
@maralorn:maralorn.demaralornBut yeah, we could of course use that heuristic. However I’d prefer to have a correct logic instead of paving over the occurences where the user can tell that something is afoot.17:25:29
@vivekanandan_ks:matrix.orgvivekanandan_ks

Oh. I'm using unstable channel. Still not seeing it when I run the nh commands.
🤔Maybe not upstreamed yet in nh?

Btw where the progress bar will be shown?

17:52:42
@k900:0upti.meK900It's not in a stable release yet17:53:24
@maralorn:maralorn.demaralorn vivekanandan_ks: Currently we have one progress bar per transfer right aligned in the tree-row of a transfer. 17:55:14
@maralorn:maralorn.demaralornBut I am currently also thinking about having one colored global progress bar in the last line which cumulates all builds and transfers.17:56:02
@vivekanandan_ks:matrix.orgvivekanandan_ksThis actually sounds great. Looking forward to it🤩17:57:37
@maralorn:maralorn.demaralornMe too. Wonder if I can find a free evening for that this year …18:01:36
26 Nov 2025
@saygo.2:tchncs.desaygo.2 The problem with optparse applicative is that forwardOptions like all other info modifiers can only be applied to the whole parser 04:24:30
@saygo.2:tchncs.desaygo.2 this causes all unparsed arguments to be treated as positionals — which is good for the nix build etc wrappers, but terrible for normal nom 04:25:15
@saygo.2:tchncs.desaygo.2 I think it might actually be the cleanest to still parse the subcommands manually and only use optparse for nom 04:26:02
@saygo.2:tchncs.desaygo.2 I could make optparse applicative work for all but then we would have to use nix build -- <nix-args> 04:33:12
@saygo.2:tchncs.desaygo.2 since after -- all args are treated as posistionals anyway so i no longer have to use forwardOptions globally 04:33:39
@saygo.2:tchncs.desaygo.2 * I could make optparse applicative work for all but then we would have to use nix build -- <nix-args> which defeats the point of a drop in wrapper 04:35:08
@saygo.2:tchncs.desaygo.2I'll try writing it so that we use the old way of parsing subcommands, but then ill still create the subcommands using optparse for the help pages to work well (and maybe autocompletion though i havent looked into that at all yet)04:36:13
@saygo.2:tchncs.desaygo.2* I'll try writing it so that we use the current way of parsing subcommands, but then ill still create the subcommands using optparse for the help pages to work well (and maybe autocompletion though i havent looked into that at all yet)04:36:34
8 Aug 2025
@0x4a6f:nixos.dev0x4A6F joined the room.07:01:22
@picnoir:alternativebit.frPicnoir changed their display name from Picnoir to Picnoir DECT 7426.12:32:56
9 Aug 2025
@seapat:matrix.orgseapat set a profile picture.14:23:15
@seapat:matrix.orgseapat 14:25:21

Show newer messages


Back to Room ListRoom Version: 9