2025/11/03

Newest at the top

2025-11-03 17:13:22 +0100FANTOM(~fantom@212.228.181.156) (Quit: Connection error?!)
2025-11-03 17:10:42 +0100deptype(~deptype@2406:b400:3a:73c2:9acb:ec9:2ab3:9aff)
2025-11-03 17:10:29 +0100deptype(~deptype@2406:b400:3a:73c2:d8b8:cae8:ab88:765a) (Remote host closed the connection)
2025-11-03 17:09:36 +0100L29Ah(~L29Ah@wikipedia/L29Ah) (Read error: Connection timed out)
2025-11-03 17:04:31 +0100prdak1prdak
2025-11-03 17:04:31 +0100prdak(~Thunderbi@user/prdak) (Ping timeout: 264 seconds)
2025-11-03 17:00:45 +0100prdak1(~Thunderbi@user/prdak) prdak
2025-11-03 16:59:51 +0100prdak(~Thunderbi@user/prdak) prdak
2025-11-03 16:51:19 +0100prdak(~Thunderbi@user/prdak) (Ping timeout: 264 seconds)
2025-11-03 16:50:40 +0100deptype(~deptype@2406:b400:3a:73c2:d8b8:cae8:ab88:765a)
2025-11-03 16:50:24 +0100deptype(~deptype@2406:b400:3a:73c2:6c77:97e3:113e:dea6) (Remote host closed the connection)
2025-11-03 16:50:20 +0100tromp(~textual@2001:1c00:3487:1b00:6ca3:baf2:b6ce:6247) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-11-03 16:45:06 +0100Zemyla(~Zemyla@72.178.108.235) Zemyla
2025-11-03 16:43:30 +0100CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Ping timeout: 256 seconds)
2025-11-03 16:43:04 +0100 <davean> haskell.nix has so many rough edges :(
2025-11-03 16:42:29 +0100 <davean> Though the haskell.nix issue matches sadly.
2025-11-03 16:42:07 +0100 <davean> dminuoso: no, I don't mean using ghc-options
2025-11-03 16:40:46 +0100FANTOM(~fantom@212.228.181.156)
2025-11-03 16:38:46 +0100haltingsolver(~cmo@2604:3d09:207f:8000::d1dc)
2025-11-03 16:38:27 +0100Zemyla(~Zemyla@72.178.108.235) (Ping timeout: 250 seconds)
2025-11-03 16:35:27 +0100 <dminuoso> Or I guess "Nix modules" rather? Not sure.
2025-11-03 16:35:16 +0100 <dminuoso> But at least I can communicate this via NixOS modules to haskell.nix
2025-11-03 16:34:56 +0100ttybitnik(~ttybitnik@user/wolper) (Quit: Fading out...)
2025-11-03 16:33:56 +0100 <dminuoso> https://github.com/input-output-hk/haskell.nix/issues/887#issuecomment-1489632156 has some details about this.
2025-11-03 16:33:19 +0100 <dminuoso> davean: Ah turns out that does not work. Seems to be an extension of https://github.com/haskell/cabal/issues/6343
2025-11-03 16:31:07 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net)
2025-11-03 16:30:35 +0100deptype(~deptype@2406:b400:3a:73c2:6c77:97e3:113e:dea6)
2025-11-03 16:30:22 +0100deptype(~deptype@2406:b400:3a:73c2:a4a3:fb37:661e:a962) (Remote host closed the connection)
2025-11-03 16:28:09 +0100Nachtgespenst(~user@user/siracusa) (Quit: Bye!)
2025-11-03 16:25:36 +0100Square(~Square4@user/square) Square
2025-11-03 16:24:57 +0100Square(~Square4@user/square) (Remote host closed the connection)
2025-11-03 16:10:49 +0100prdak1prdak
2025-11-03 16:10:49 +0100prdak(~Thunderbi@user/prdak) (Ping timeout: 264 seconds)
2025-11-03 16:10:39 +0100deptype(~deptype@2406:b400:3a:73c2:a4a3:fb37:661e:a962)
2025-11-03 16:10:22 +0100Zemyla(~Zemyla@72.178.108.235) Zemyla
2025-11-03 16:10:20 +0100deptype(~deptype@2406:b400:3a:73c2:422:9c14:cc52:da31) (Remote host closed the connection)
2025-11-03 16:08:13 +0100prdak1(~Thunderbi@user/prdak) prdak
2025-11-03 16:07:59 +0100trickard_(~trickard@cpe-52-98-47-163.wireline.com.au)
2025-11-03 16:07:45 +0100trickard(~trickard@cpe-52-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-11-03 16:02:27 +0100 <davean> dminuoso: I would specificly recomend setting profiling: true in your cabal.project before entering the flake
2025-11-03 16:02:23 +0100ezzieyguywuf(~Unknown@user/ezzieyguywuf) ezzieyguywuf
2025-11-03 15:58:36 +0100 <davean> I think dminuoso can fix this either by setting profiling in cabal.project or in the flake with configureArgs
2025-11-03 15:58:35 +0100Zemyla(~Zemyla@72.178.108.235) (Ping timeout: 250 seconds)
2025-11-03 15:57:52 +0100 <davean> right, it builds a build way one time usually. I'm addressing why I think haskell.nix is breaking it
2025-11-03 15:57:17 +0100 <tomsmeding> makes sense; I was just arguing against "cabal usually won't rebuild something for profiling"
2025-11-03 15:56:48 +0100 <davean> yes because its a different build config
2025-11-03 15:56:26 +0100 <tomsmeding> if I use `cabal build --enable-profiling` on a project where I have not done so before, cabal definitely starts rebuidling the world with profiling.
2025-11-03 15:55:41 +0100 <davean> dminuoso: no, profiling is a build option for GHC, cabal usually won't rebuild something for profiling, it builts it the first time for it.
2025-11-03 15:53:32 +0100Zemyla(~Zemyla@72.178.108.235) Zemyla
2025-11-03 15:44:39 +0100trickard_trickard