nix-output-monitor - Public Room Timeline

	nix-output-monitor	93 Members
	https://github.com/maralorn/nix-output-monitor	30 Servers

Load older messages

Sender	Message	Time
27 Sep 2025
	@kongrooparadox:matrix.org left the room.	20:29:32
28 Sep 2025
	martijn joined the room.	12:50:28
30 Sep 2025
	ruby left the room.	01:50:26
3 Oct 2025
	@moleksiak:matrix.org joined the room.	23:18:11
	@moleksiak:matrix.org left the room.	23:24:15
7 Oct 2025
	martijn removed their profile picture.	10:54:39
	martijn set a profile picture.	10:56:09
8 Oct 2025
Sandro 🐧	I am encountering the following build failure on nixos-unstable: Building library for nix-output-monitor-2.1.6... [ 1 of 25] Compiling Data.Sequence.Strict ( lib/Data/Sequence/Strict.hs, dist/build/Data/Sequence/Strict.o, dist/build/Data/Sequence/Strict.dyn_o ) [ 2 of 25] Compiling NOM.Builds ( lib/NOM/Builds.hs, dist/build/NOM/Builds.o, dist/build/NOM/Builds.dyn_o ) [ 3 of 25] Compiling NOM.Error ( lib/NOM/Error.hs, dist/build/NOM/Error.o, dist/build/NOM/Error.dyn_o ) [ 4 of 25] Compiling NOM.NixMessage.JSON ( lib/NOM/NixMessage/JSON.hs, dist/build/NOM/NixMessage/JSON.o, dist/build/NOM/NixMessage/JSON.dyn_o ) [ 5 of 25] Compiling NOM.NixMessage.OldStyle ( lib/NOM/NixMessage/OldStyle.hs, dist/build/NOM/NixMessage/OldStyle.o, dist/build/NOM/NixMessage/OldStyle.dyn_o ) [ 6 of 25] Compiling NOM.Parser ( lib/NOM/Parser.hs, dist/build/NOM/Parser.o, dist/build/NOM/Parser.dyn_o ) [ 7 of 25] Compiling NOM.Parser.JSON ( lib/NOM/Parser/JSON.hs, dist/build/NOM/Parser/JSON.o, dist/build/NOM/Parser/JSON.dyn_o ) [ 8 of 25] Compiling NOM.Print.Table ( lib/NOM/Print/Table.hs, dist/build/NOM/Print/Table.o, dist/build/NOM/Print/Table.dyn_o ) [ 9 of 25] Compiling NOM.Print.Tree ( lib/NOM/Print/Tree.hs, dist/build/NOM/Print/Tree.o, dist/build/NOM/Print/Tree.dyn_o ) [10 of 25] Compiling NOM.State.CacheId ( lib/NOM/State/CacheId.hs, dist/build/NOM/State/CacheId.o, dist/build/NOM/State/CacheId.dyn_o ) [11 of 25] Compiling NOM.State.CacheId.Set ( lib/NOM/State/CacheId/Set.hs, dist/build/NOM/State/CacheId/Set.o, dist/build/NOM/State/CacheId/Set.dyn_o ) [12 of 25] Compiling NOM.State.CacheId.Map ( lib/NOM/State/CacheId/Map.hs, dist/build/NOM/State/CacheId/Map.o, dist/build/NOM/State/CacheId/Map.dyn_o ) [13 of 25] Compiling NOM.State.Tree ( lib/NOM/State/Tree.hs, dist/build/NOM/State/Tree.o, dist/build/NOM/State/Tree.dyn_o ) [14 of 25] Compiling NOM.StreamParser ( lib/NOM/StreamParser.hs, dist/build/NOM/StreamParser.o, dist/build/NOM/StreamParser.dyn_o ) [15 of 25] Compiling NOM.Update.Monad.CacheBuildReports ( lib/NOM/Update/Monad/CacheBuildReports.hs, dist/build/NOM/Update/Monad/CacheBuildReports.o, dist/build/NOM/Update/Monad/CacheBuildReports.dyn_o ) [16 of 25] Compiling NOM.Update.Monad ( lib/NOM/Update/Monad.hs, dist/build/NOM/Update/Monad.o, dist/build/NOM/Update/Monad.dyn_o ) [17 of 25] Compiling NOM.Util ( lib/NOM/Util.hs, dist/build/NOM/Util.o, dist/build/NOM/Util.dyn_o ) [18 of 25] Compiling NOM.State ( lib/NOM/State.hs, dist/build/NOM/State.o, dist/build/NOM/State.dyn_o ) [19 of 25] Compiling NOM.State.Sorting ( lib/NOM/State/Sorting.hs, dist/build/NOM/State/Sorting.o, dist/build/NOM/State/Sorting.dyn_o ) [20 of 25] Compiling NOM.Update ( lib/NOM/Update.hs, dist/build/NOM/Update.o, dist/build/NOM/Update.dyn_o ) lib/NOM/Update.hs:172:18: error: [GHC-30606] [-Wredundant-constraints, Werror=redundant-constraints] Redundant constraint: UpdateMonad m In the type signature for: processResult :: NixOldStyleMessage -> ProcessingT m Bool \| 172 \| processResult :: (UpdateMonad m) => NixOldStyleMessage -> ProcessingT m Bool \| ^^^^^^^^^^^^^^^	19:43:12
maralorn	With the flake?	19:51:51
maralorn	Or like nom is currently broken on hydra?	19:52:25
maralorn	Looks like the flake because -Werror should not be active in production.	19:52:55
maralorn	Okay	19:54:16
maralorn	Well, thanks for the report but this will probably come up for me anyway on friday when my renovate bot bumps the nixos-unstable pin on the nom repo. 😄	19:55:59
Sandro 🐧	Yeah, the flake actually, I forgot	19:56:13
Sandro 🐧	Maybe I should switch over to the nixpkgs package again 😅	19:56:18
maralorn	I mean it’s not like nom development speed is so high that using the flake buys you much. 😄	19:57:15
maralorn	What’s confusing me, however is the error message itself.	19:58:24
maralorn	I really can’t imagine how this code could compile without this constraint.	19:58:51
maralorn	Oh, I take that back.	19:59:16
maralorn	Cool	19:59:35
Sandro 🐧	Probably from something even last year where I was waiting for some fix or so. If I can't remember it might not even be necessary	20:01:11
12 Oct 2025
	Anton (he/him) changed their display name from Anton to Anton (he/him).	13:17:12
13 Oct 2025
	vivekanandan_ks joined the room.	18:56:34
18 Oct 2025
	@dawnofmidnight:catgirl.cloud changed their display name from dawnofmidnight to whispers.	05:34:34
23 Oct 2025
Philip Taron (UTC-8)	I just opened https://github.com/NixOS/nixpkgs/pull/454982 to allow `nom` to pin a specific Nix or Lix version.	17:51:31
Philip Taron (UTC-8)	My usecase is to use `nom` in `nixos-rebuild` and `nixos-rebuild-ng`, both of which are particular about pinning Nix to a specific version before they go about their work.	17:52:24
28 Oct 2025
	lillecarl joined the room.	22:01:48
2 Nov 2025
	@dawnofmidnight:catgirl.cloud changed their display name from whispers to whispers (it/fae).	17:58:08
3 Nov 2025
loudgolem	wow, never knew this was a thing `asciinema-3.0.1 (buildPhase) ⏱ 4m21s (∅ 6m31s)` i.e the ETA. I recently came across some pr which fixes generation of build reports I guess that allows tracking this.	18:14:09
loudgolem	* wow, never knew this was a thing `asciinema-3.0.1 (buildPhase) ⏱ 4m21s (∅ 6m31s)` i.e the ETA (6m31s). I recently came across some pr which fixes generation of build reports I guess that allows tracking this.	18:20:02

Show newer messages

Back to Room ListRoom Version: 9