| 2 Aug 2025 |
 magic_rb | (and anyway, i wanna write my own for fun and profit) | 11:27:01 |
 emily | I think they should if you give the container a userns which you should probably do for isolation anyway l | 11:27:24 |
| emily | but sure :) | 11:27:27 |
| magic_rb | my goal with this is starting with replacing much of the shell script non sense in nixng with small haskell binaries | 11:28:11 |
| magic_rb | been planning to do that for a while | 11:28:17 |
| magic_rb | with UPX on top, it goes from 3.6MB to 700KB | 11:29:53 |
| magic_rb | nice | 11:29:54 |
| magic_rb | we shold have a UPX post build hook thing | 11:30:16 |
| magic_rb | this is actually nice, writeHaskell actually creates a equally small binary | 11:48:02 |
|  @froggymoded:matrix.org left the room. | 18:13:15 |
| 3 Aug 2025 |
 sterni (he/him) | MangoIV: will you need htree for GHC < 9.10 going forward? | 10:39:36 |
 MangoIV | No. this is intended.. Thank you for pining but since this has come up the second time now, I think I'm registered for maintainer, let me just fix it if it breaks in the future. :) | 10:41:18 |
| MangoIV | (don't want you to be blocked on things like this :3) | 10:41:32 |
| sterni (he/him) | MangoIV: well we're far from blocking on anything, I was just cleaning up some stuff | 10:50:39 |
| sterni (he/him) | Would be great if someone could look into this since there is no known fix yet https://github.com/typeclasses/chell/issues/5 | 10:50:54 |
|  prescientmoon changed their display name from Adriel to prescientmoon. | 14:31:42 |
| 4 Aug 2025 |
 Marc Jakobi | Has anyone else noticed a significant increase in memory when compiling Haskell packages with ghc 9.8.4 compared to ghc 9.6.6? I haven't been able to pinpoint it yet and I can't reproduce it outside of nix builds. | 09:45:42 |
 ners | Does this happen on the same nixpkgs pin, e.g. nix build nixpkgs#haskell.packages.ghc984.rhine vs nix build nixpkgs#haskell.packages.ghc966.rhine? | 10:09:07 |
| Marc Jakobi | In reply to @ners:nixos.dev
Does this happen on the same nixpkgs pin, e.g. nix build nixpkgs#haskell.packages.ghc984.rhine vs nix build nixpkgs#haskell.packages.ghc966.rhine? It doesn't even happen for all packages. I'm trying to build the same package with ghc 9.6, but it's failing to build singletons-th (or singletons-th_3_5), which is one of the dependencies - which kind of adds to my suspicion that this may be a template-haskell regression. | 14:28:51 |
| Marc Jakobi | Yep, no matter how I try to override or jailbreak packages, I can't seem escape dependency hell if I use another ghc version. | 15:13:23 |
 Teo (he/him) | Are you able to reproduce this outside of nix? Might be good to open a GHC ticket if you can confirm it's a GHC issue | 15:31:08 |
| Teo (he/him) | Oh you already said you couldn't reproduce it outside of nix builds | 15:34:38 |
| sterni (he/him) | teo (they/he): I mean what you could put on your GHC review pile is my never reviewed MR :p https://gitlab.haskell.org/ghc/ghc/-/merge_requests/13932 | 16:30:06 |
| Teo (he/him) | Will do! Feel free to tag me in the future too. It's a real shame that that slipped through the cracks | 16:31:20 |
| Teo (he/him) | I hadn't realized you were already trying to build a stage2 compiler for these configurations. I know that isn't supported in hadrian in general and that's being fixed in https://gitlab.haskell.org/ghc/ghc/-/merge_requests/11444. But maybe it would be supported in this case and something is just going wrong with this flag. I'll look into it and see if there's an easy fix | 16:33:24 |
| sterni (he/him) | I was convinced it worked, but when I checked the log I saw that only ghc the library is built in _build/stage1/compiler just before it finishes. Checking ghc --info revealed that it's indeed just Stage1 :( | 16:48:18 |
| Teo (he/him) | Ah annoying! | 16:56:45 |
 oak 🏳️🌈♥️ | Is it possible to ignore specific testcases when packaging a Haskell package, instead of disabling all the tests with dontCheck? With overrideCabal? | 19:03:10 |
| oak 🏳️🌈♥️ | Found a solution, modify testFlags through overrideCabal | 21:09:34 |
| 5 Aug 2025 |
| Marc Jakobi | I think I've narrowed the high memory consumption down to the use of inline-python's marshalling functions (fromPy, ...).
Will investigate further... | 06:59:22 |
