2026/02/11

Newest at the top

2026-02-11 22:29:19 +0100PorfirioAguilar(~PorfirioA@user/PorfirioAguilar) PorfirioAguilar
2026-02-11 22:27:26 +0100 <haskellbridge> <sm> but I think your paste showed the path of it, you could try just deleting those files ?
2026-02-11 22:26:01 +0100tromp(~textual@2001:1c00:3487:1b00:5913:697:5f95:d198)
2026-02-11 22:25:28 +0100 <haskellbridge> <sm> I feel there's an out of date build of process somewhere getting used by that particular project (and the package version number may not tell the whole story)
2026-02-11 22:25:11 +0100 <perryprog> sm, it just kills ~/.ghcup I think
2026-02-11 22:23:53 +0100 <haskellbridge> <maerwald> No, it doesn't delete ghc or cabal dirs
2026-02-11 22:23:27 +0100 <int-e> LOL, https://github.com/haskell/ghcup-hs/blob/master/lib-opt/GHCup/OptParse/Nuke.hs#L78
2026-02-11 22:23:17 +0100confusedalex(~confuseda@user/confusedalex) confusedalex
2026-02-11 22:21:57 +0100housemate(~housemate@202.7.248.67) housemate
2026-02-11 22:21:16 +0100 <haskellbridge> <sm> there's nuke and there's NUKE FROM ORBIT
2026-02-11 22:20:41 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-02-11 22:19:19 +0100 <haskellbridge> <sm> I don't know what that does, did it remove your ~/.ghc, ~/.cabal, all haskell tools from PATH etc ?
2026-02-11 22:17:47 +0100 <perryprog> I did ghcup nuke
2026-02-11 22:17:36 +0100 <haskellbridge> <sm> perryprog what did you nuke ?
2026-02-11 22:17:22 +0100housemate(~housemate@202.7.248.67) (Quit: https://ineedsomeacidtocalmmedown.space/)
2026-02-11 22:15:56 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-11 22:14:25 +0100confusedalex(~confuseda@user/confusedalex) (Ping timeout: 264 seconds)
2026-02-11 22:10:55 +0100emmanuelux(~em@user/emmanuelux) emmanuelux
2026-02-11 22:07:55 +0100tromp(~textual@2001:1c00:3487:1b00:5913:697:5f95:d198) (Quit: My iMac has gone to sleep. ZZZzzz…)
2026-02-11 22:06:55 +0100ChaiTRex(~ChaiTRex@user/chaitrex) ChaiTRex
2026-02-11 22:06:29 +0100ChaiTRex(~ChaiTRex@user/chaitrex) (Remote host closed the connection)
2026-02-11 22:05:44 +0100califax(~califax@user/califx) califx
2026-02-11 22:05:28 +0100califax(~califax@user/califx) (Remote host closed the connection)
2026-02-11 22:04:49 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 250 seconds)
2026-02-11 22:01:54 +0100 <brioche> I could do this by disabling close_fds in CreateProcess, but I don't want the other FDs to stay open. I just want to keep a specific list of FDs open.
2026-02-11 22:00:33 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-11 22:00:18 +0100 <brioche> Yeah, a pipe for example
2026-02-11 21:58:41 +0100 <EvanR> the other FDs?
2026-02-11 21:57:11 +0100Googulator54Googulator
2026-02-11 21:55:56 +0100 <brioche> I know that createProcess allows to specify a stdin, stdout and stderr FDs, but what about the other FDs?
2026-02-11 21:55:22 +0100 <brioche> Does anyone here know how to spawn a process with a given specific file descriptor?
2026-02-11 21:50:17 +0100Googulator(~Googulato@2a01-036d-0106-216f-6164-ec92-51a0-9cde.pool6.digikabel.hu) (Ping timeout: 272 seconds)
2026-02-11 21:50:03 +0100brioche(~username@user/brioche) brioche
2026-02-11 21:49:53 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-02-11 21:45:56 +0100Googulator54(~Googulato@84-236-65-138.pool.digikabel.hu)
2026-02-11 21:45:09 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-11 21:43:57 +0100divlamir(~divlamir@user/divlamir) divlamir
2026-02-11 21:43:41 +0100divlamir(~divlamir@user/divlamir) (Read error: Connection reset by peer)
2026-02-11 21:34:49 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2026-02-11 21:30:45 +0100 <perryprog> nuke did not fix :(
2026-02-11 21:29:46 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-11 21:21:51 +0100target_i(~target_i@user/target-i/x-6023099) target_i
2026-02-11 21:16:32 +0100Enrico63(~Enrico63@host-79-22-157-220.retail.telecomitalia.it) (Quit: Client closed)
2026-02-11 21:13:04 +0100 <perryprog> well, yes
2026-02-11 21:12:59 +0100 <EvanR> so the entire body of the program can a priori be implicated
2026-02-11 21:12:29 +0100 <EvanR> I don't think code knows what a line is... it's about the values being passed to the e.g. readCreateProcessWithExitCode... or some FFI call, because if there is corruption the crash can easily be non-locally triggered
2026-02-11 21:11:39 +0100 <perryprog> intermediate bug theorem is hilarious
2026-02-11 21:11:31 +0100 <perryprog> the problem lines of code are literally identical :(
2026-02-11 21:11:05 +0100 <EvanR> slowly mutate the non working one to the working one, and eventually it has to flip. (intermediate bug theorem)
2026-02-11 21:10:22 +0100 <EvanR> same version different projects different results... even after cloning them and rebuilding everything, then it really seems like you have more usage patterns to bisect