!yxFWYdmeLrdzdoIrcE:maralorn.de

nix-output-monitor

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

Load older messages


SenderMessageTime
4 Dec 2025
@emma:rory.gayEmma [it/its]clipboard.png
Download clipboard.png
23:34:44
@emma:rory.gayEmma [it/its](this is on nom main)23:34:51
@emma:rory.gayEmma [it/its]oh wait i just realised im an idiot and updated my build script to use nom main but im not using the script lol23:37:22
@emma:rory.gayEmma [it/its]yeah switched to nom main, seesm it was a false alarm and is infact fixed :)23:41:12
@emma:rory.gayEmma [it/its]ive been confused about it for the last hour or so lol23:43:19
5 Dec 2025
@maralorn:maralorn.demaralornYeah.10:01:54
@maralorn:maralorn.demaralornThat stupid detection is currently a release blocker because I think what I did regresses some situations which previously worked fine.10:03:04
@emma:rory.gayEmma [it/its] ran out of memory overnight during a buid, now im trying with -j1 and it seems its not perfectly reliable either (still in that same nix shell): 10:17:02
@emma:rory.gayEmma [it/its]clipboard.png
Download clipboard.png
10:17:08
@emma:rory.gayEmma [it/its]but this is a bit of an odd case i suppose10:17:54
@maralorn:maralorn.demaralornStill sucks.10:18:34
@maralorn:maralorn.demaralornProblem is I really need an internal-json log of an offending build to figure this out.10:19:09
@emma:rory.gayEmma [it/its]hmm, if you can hack in support for passing a wrapper command (with maybe an arg or 2) i could probably bridge the nix logs as requested by nom to a matrix room10:21:17
@emma:rory.gayEmma [it/its]or store them in a file somewhere...10:21:55
@emma:rory.gayEmma [it/its]with the former i'd expect you to be able to tail my logs in ~realtime, give or take federation lag10:26:00
@emma:rory.gayEmma [it/its]i dont expect this to finish in the next couple of hours soo... ill go fix up some packaging woes and see if i can build a simple matrix bridge for logs10:37:54
@saygo.2:tchncs.desaygo.2 i think you can just use tee to split the stdout/stderr streams 10:41:24
@saygo.2:tchncs.desaygo.2 just use plain nom with a pipe and tee 10:41:40
@saygo.2:tchncs.desaygo.2not enough of a shell wizard to give you the exact commands but it should be possible10:42:18
@emma:rory.gayEmma [it/its]im using nom as wrapper by itself ^^'10:42:37
@maralorn:maralorn.demaralorn Emma [it/its]: We don’t need a matrix bridge. 😄 10:43:21
@maralorn:maralorn.demaralornJust do what saygo.2 says and dm me the log the next time you see this happening.10:44:03
@maralorn:maralorn.demaralorn(or post it here)10:44:14
@maralorn:maralorn.demaralorn nom build <foo> is basically the same is nix build -v --log-format internal-json <foo> |& nom --json 10:45:25
@emma:rory.gayEmma [it/its]ah10:46:04
@maralorn:maralorn.demaralorn So make that nix build -v --log-format internal-json <foo> |& tee nom.log | nom --json. 10:46:06
@emma:rory.gayEmma [it/its]ill wait for nodejs to finish building and ill get to it then :P10:46:20
@emma:rory.gayEmma [it/its]

curl -s https://rory.gay/nom.log | nom --json

that was quick lol

10:58:01
@emma:rory.gayEmma [it/its]took me less than a minute to reproduce10:58:10
@emma:rory.gayEmma [it/its] nix build .#nixosConfigurations.Rory-desktop.config.system.build.toplevel -j1 --show-trace --keep-going --accept-flake-config -L -v --log-format internal-json |& tee ~/nom.log | nom --json 10:58:28

Show newer messages


Back to Room ListRoom Version: 9