2025/05/18

2025-05-18 00:02:19 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 00:02:42 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 00:05:50 +0200machinedgod(~machinedg@d108-173-18-100.abhsia.telus.net) machinedgod
2025-05-18 00:06:37 +0200 <kaol> cabal v2 sucks. I want to edit one file and I can't figure how to do an incremental compile. It always worked just fine with v1. I seem to be stuck in a hell of waiting for 150 modules to build every time instead.
2025-05-18 00:08:02 +0200 <monochrom> I never experieinced that.
2025-05-18 00:08:20 +0200 <kaol> "cabal build > Up to date" no it isn't you idiot program.
2025-05-18 00:12:53 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds)
2025-05-18 00:16:36 +0200 <kaol> Okay, I switched from bumping the project version number in cabal to just twiddling with build-depends instead. That avoids doing the full compile at least. Now I just change base's upper bound every time to trigger the check to see that one module that's changed.
2025-05-18 00:16:51 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Quit: peterbecich)
2025-05-18 00:17:12 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-05-18 00:18:12 +0200jmcantrell(~weechat@user/jmcantrell) jmcantrell
2025-05-18 00:18:30 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 00:18:53 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 00:20:43 +0200Frostillicus(~Frostilli@pool-71-174-119-56.bstnma.fios.verizon.net)
2025-05-18 00:24:39 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 00:25:00 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 00:25:30 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-05-18 00:26:17 +0200wootehfoot(~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer)
2025-05-18 00:26:20 +0200 <hololeap> I've seen doctests change some obscure thing and cause a bunch of modules to get rebuilt
2025-05-18 00:28:42 +0200machinedgod(~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 272 seconds)
2025-05-18 00:28:51 +0200 <kaol> And even that build-dependency trick is not quite clean. It triggers dependency checks for all of my executables and libraries, not just the one I'm editing. Those take time.
2025-05-18 00:29:58 +0200 <kaol> And all I'm really doing is just cabal build. This is the kind of usability issues that make me think that cabal developers never use the program themselves.
2025-05-18 00:30:33 +0200 <EvanR> you're changing the version numbers on base but don't want it to recompile everything?
2025-05-18 00:30:53 +0200 <kaol> I'm only doing it to have it notice a change to one module file.
2025-05-18 00:31:04 +0200tromp(~textual@2001:1c00:3487:1b00:ace7:b293:8f4:7479) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-05-18 00:31:10 +0200 <kaol> The upper bound. I'm not obviously changing ghc in between.
2025-05-18 00:31:21 +0200 <EvanR> changing 1 module file shouldn't trigger a full rebuild, unless it's something everything depends on
2025-05-18 00:31:40 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 00:31:46 +0200 <kaol> Changing 1 module file gets completely ignored. That's the problem.
2025-05-18 00:31:55 +0200 <EvanR> o_O
2025-05-18 00:31:59 +0200 <kaol> I'm manipulating my cabal file just to make cabal build catch that.
2025-05-18 00:32:03 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 00:32:28 +0200 <EvanR> are you sure that file is listed in the cabal other modules
2025-05-18 00:32:30 +0200notzmv(~daniel@user/notzmv) (Ping timeout: 272 seconds)
2025-05-18 00:34:39 +0200 <Clint> as opposed to exposed-modules?
2025-05-18 00:34:41 +0200 <kaol> It makes no difference whether I have it in other-modules or not.
2025-05-18 00:34:55 +0200 <kaol> v1 never cared about that.
2025-05-18 00:35:41 +0200 <monochrom> I guess with 150 modules, one is not inclined to list them anywhere.
2025-05-18 00:36:19 +0200 <kaol> I just want the behavior that cabal build does if I have a compile error in one module. It works as expected as long as I don't have it compile successfully.
2025-05-18 00:36:38 +0200 <kaol> As long as it is in that state I can change any module and it sees the change.
2025-05-18 00:36:53 +0200 <kaol> But once it compiles once, it never checks any files for changes again.
2025-05-18 00:36:58 +0200 <kaol> Unless I edit my cabal file.
2025-05-18 00:37:19 +0200 <kaol> Which triggers all sorts of dependency checks as well which is slow.
2025-05-18 00:38:32 +0200 <kaol> If cabal build is not the supposed way to use cabal then what is?
2025-05-18 00:38:41 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 00:38:45 +0200 <kaol> If I can't even build my project anymore after it succeeds once?
2025-05-18 00:39:05 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 00:40:14 +0200Frostillicus(~Frostilli@pool-71-174-119-56.bstnma.fios.verizon.net) (Ping timeout: 260 seconds)
2025-05-18 00:46:07 +0200 <sm> kaol, that's not working as intended. It'll take some work, but maybe you can minimise it to identify the cause, or share the repo
2025-05-18 00:46:25 +0200__monty__(~toonn@user/toonn) (Quit: leaving)
2025-05-18 00:47:31 +0200 <sm> there's also the #hackage channel where cabal developers are
2025-05-18 00:49:09 +0200notzmv(~daniel@user/notzmv) notzmv
2025-05-18 00:49:47 +0200 <sm> also mention your cabal --version
2025-05-18 00:50:30 +0200Guest11(~Guest11@syn-024-165-041-231.res.spectrum.com)
2025-05-18 00:52:13 +0200 <kaol> https://gitlab.com/piperka/piperka and cabal-install version 3.10.3.0
2025-05-18 00:55:55 +0200Frostillicus(~Frostilli@pool-71-174-119-56.bstnma.fios.verizon.net)
2025-05-18 00:56:25 +0200 <sm> kaol, this project doesn't build easily, I wonder which ghc --version you have
2025-05-18 00:56:46 +0200 <sm> 9.6 I guess
2025-05-18 00:58:07 +0200 <sm> no good.. I would try to reproduce your issue, but I can't resolve your dependencies
2025-05-18 00:58:35 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 00:58:56 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 00:59:08 +0200 <kaol> I'm using 9.6.6 currently.
2025-05-18 01:00:49 +0200Frostillicus(~Frostilli@pool-71-174-119-56.bstnma.fios.verizon.net) (Ping timeout: 252 seconds)
2025-05-18 01:07:18 +0200Guest11(~Guest11@syn-024-165-041-231.res.spectrum.com) (Ping timeout: 240 seconds)
2025-05-18 01:08:42 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 01:09:05 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 01:10:12 +0200 <sm> --allow-newer gets farther, but I failed to make cabal build text-icu on mac. But try simplifying your project until it works. Changing a .hs file should definitely trigger recompilation
2025-05-18 01:11:20 +0200Guest11(~Guest11@syn-024-165-041-231.res.spectrum.com)
2025-05-18 01:14:40 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 01:15:00 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 01:17:18 +0200Guest57(~Guest11@syn-024-165-041-231.res.spectrum.com)
2025-05-18 01:18:06 +0200Guest11(~Guest11@syn-024-165-041-231.res.spectrum.com) (Ping timeout: 240 seconds)
2025-05-18 01:21:00 +0200Lord_of_Life_(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2025-05-18 01:21:39 +0200Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 244 seconds)
2025-05-18 01:21:48 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 264 seconds)
2025-05-18 01:22:22 +0200Lord_of_Life_Lord_of_Life
2025-05-18 01:22:59 +0200 <kaol> "cabal install --only-dependencies --force-reinstalls --overwrite-policy=always" works as well to clear whatever's blocking the module file change check.
2025-05-18 01:23:44 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) bitdex
2025-05-18 01:25:04 +0200 <kaol> No wait, that didn't. I still needed to edit my cabal file.
2025-05-18 01:29:50 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 268 seconds)
2025-05-18 01:36:36 +0200 <Leary> kaol: Your `hs-source-dirs` are overlapping between components. This can cause problems due to the way GHC searches for modules; try separating them.
2025-05-18 01:38:45 +0200 <sm> 🚀
2025-05-18 01:39:42 +0200 <Leary> (I'm not claiming this is the solution, but it's the thing that looks most wrong in the .cabal file)
2025-05-18 01:41:44 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-05-18 01:42:33 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 01:42:54 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 01:43:26 +0200hiredman(~hiredman@frontier1.downey.family) (Quit: Lost terminal)
2025-05-18 01:44:43 +0200ljdarj1(~Thunderbi@user/ljdarj) ljdarj
2025-05-18 01:48:29 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 260 seconds)
2025-05-18 01:48:29 +0200ljdarj1ljdarj
2025-05-18 01:50:13 +0200j1n37(~j1n37@user/j1n37) (Ping timeout: 248 seconds)
2025-05-18 01:50:44 +0200j1n37(~j1n37@user/j1n37) j1n37
2025-05-18 01:50:48 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 01:51:09 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 01:53:51 +0200sus0(zero@user/zeromomentum) zeromomentum
2025-05-18 01:56:50 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 01:57:10 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 02:02:51 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 02:03:11 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 02:03:46 +0200jespada(~jespada@r179-25-150-22.dialup.adsl.anteldata.net.uy) (Ping timeout: 252 seconds)
2025-05-18 02:05:36 +0200acidjnk(~acidjnk@p200300d6e71c4f65f1ead88f57001215.dip0.t-ipconnect.de) (Ping timeout: 272 seconds)
2025-05-18 02:08:02 +0200sprotte24(~sprotte24@p200300d16f06fd00c9f6fa4fdf16930b.dip0.t-ipconnect.de) (Quit: Leaving)
2025-05-18 02:12:17 +0200Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.)
2025-05-18 02:14:52 +0200craunts(~craunts@136.158.8.87)
2025-05-18 02:32:06 +0200Guest57(~Guest11@syn-024-165-041-231.res.spectrum.com) (Ping timeout: 240 seconds)
2025-05-18 02:32:59 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 02:33:20 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 02:34:00 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 276 seconds)
2025-05-18 02:35:57 +0200Guest11(~Guest11@syn-024-165-041-231.res.spectrum.com)
2025-05-18 02:47:06 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 02:47:28 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 02:53:27 +0200harveypwca(~harveypwc@2601:246:d080:f6e0:27d6:8cc7:eca9:c46c) (Quit: Leaving)
2025-05-18 02:55:37 +0200Square2(~Square@user/square) (Ping timeout: 265 seconds)
2025-05-18 02:59:48 +0200 <sm> watch = ["util", "exec", "--", "sh", "-c", """
2025-05-18 02:59:49 +0200 <sm> watchexec --wrap-process=session --no-vcs-ignore --ignore .jj/working_copy/working_copy.lock -c clear --bell "date; echo; jj --no-pager $@"
2025-05-18 02:59:49 +0200 <sm> """, ""]
2025-05-18 03:01:49 +0200end(~end@user/end/x-0094621) (Ping timeout: 252 seconds)
2025-05-18 03:02:10 +0200bcksl(~bcksl@user/bcksl) (Ping timeout: 260 seconds)
2025-05-18 03:02:47 +0200sus0(zero@user/zeromomentum) (Ping timeout: 252 seconds)
2025-05-18 03:05:41 +0200 <sm> I forgot a `--watch .jj` in there, more efficient
2025-05-18 03:06:05 +0200 <sm> now I can have an updating log, op log etc like in Martin's video
2025-05-18 03:09:59 +0200 <sm> and I can keep an eye on what other jj tools (like VJJ) are doing
2025-05-18 03:10:29 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Quit: peterbecich)
2025-05-18 03:11:11 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-05-18 03:25:17 +0200craunts7(~craunts@136.158.8.87)
2025-05-18 03:25:22 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 03:25:44 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 03:26:11 +0200bcksl(~bcksl@user/bcksl) bcksl
2025-05-18 03:27:06 +0200craunts(~craunts@136.158.8.87) (Ping timeout: 252 seconds)
2025-05-18 03:27:07 +0200craunts7craunts
2025-05-18 03:27:10 +0200ttybitnik(~ttybitnik@user/wolper) (Quit: Fading out...)
2025-05-18 03:27:12 +0200xff0x(~xff0x@om126236151042.32.openmobile.ne.jp)
2025-05-18 03:31:14 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 03:31:35 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 03:35:21 +0200end(~end@user/end/x-0094621) end^
2025-05-18 03:36:21 +0200xff0x(~xff0x@om126236151042.32.openmobile.ne.jp) (Read error: Connection reset by peer)
2025-05-18 03:41:40 +0200xff0x(~xff0x@om126236151042.32.openmobile.ne.jp)
2025-05-18 03:44:55 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 03:45:16 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 03:46:09 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 276 seconds)
2025-05-18 03:48:30 +0200hiecaq(~hiecaq@user/hiecaq) hiecaq
2025-05-18 03:54:54 +0200xff0x(~xff0x@om126236151042.32.openmobile.ne.jp) (Read error: Connection reset by peer)
2025-05-18 03:58:03 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-05-18 04:01:25 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 04:01:46 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 04:05:03 +0200op_4(~tslil@user/op-4/x-9116473) (Remote host closed the connection)
2025-05-18 04:05:39 +0200op_4(~tslil@user/op-4/x-9116473) op_4
2025-05-18 04:05:47 +0200joeyadams(~textual@syn-162-154-010-038.res.spectrum.com)
2025-05-18 04:14:06 +0200manwithluck(~manwithlu@2a09:bac5:5082:2387::38a:10) (Ping timeout: 276 seconds)
2025-05-18 04:14:09 +0200td_(~td@i53870928.versanet.de) (Ping timeout: 245 seconds)
2025-05-18 04:16:02 +0200td_(~td@i5387091A.versanet.de) td_
2025-05-18 04:16:14 +0200 <ski> oh .. sorry, for some reason i missed the paste, Leary
2025-05-18 04:19:19 +0200 <Leary> No worries.
2025-05-18 04:24:02 +0200JuanDaugherty(~juan@user/JuanDaugherty) JuanDaugherty
2025-05-18 04:25:11 +0200gmg(~user@user/gehmehgeh) (Remote host closed the connection)
2025-05-18 04:29:14 +0200 <ski> i was reminded of `IVar's, but it doesn't look like what you're doing is that similar to that (except `Identified', slightly)
2025-05-18 04:31:30 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 04:31:52 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 04:40:33 +0200xff0x(~xff0x@om126236151042.32.openmobile.ne.jp)
2025-05-18 04:46:33 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 252 seconds)
2025-05-18 04:54:47 +0200JuanDaugherty(~juan@user/JuanDaugherty) (Quit: praxis.meansofproduction.biz (juan@acm.org))
2025-05-18 04:55:49 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-05-18 04:56:09 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-18 05:00:32 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Read error: Connection reset by peer)
2025-05-18 05:00:32 +0200chexum(~quassel@gateway/tor-sasl/chexum) (Remote host closed the connection)
2025-05-18 05:00:32 +0200chiselfuse(~chiselfus@user/chiselfuse) (Remote host closed the connection)
2025-05-18 05:00:32 +0200califax(~califax@user/califx) (Remote host closed the connection)
2025-05-18 05:00:32 +0200ChaiTRex(~ChaiTRex@user/chaitrex) (Remote host closed the connection)
2025-05-18 05:00:52 +0200califax(~califax@user/califx) califx
2025-05-18 05:00:55 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) bitdex
2025-05-18 05:00:58 +0200chexum(~quassel@gateway/tor-sasl/chexum) chexum
2025-05-18 05:01:02 +0200ChaiTRex(~ChaiTRex@user/chaitrex) ChaiTRex
2025-05-18 05:01:10 +0200chiselfuse(~chiselfus@user/chiselfuse) chiselfuse
2025-05-18 05:01:45 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-05-18 05:04:11 +0200Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 265 seconds)
2025-05-18 05:05:24 +0200ystael(~ystael@user/ystael) (Ping timeout: 245 seconds)