2026/01/24

Newest at the top

2026-01-24 14:17:25 +0100monochrom(trebla@216.138.220.146) (Ping timeout: 264 seconds)
2026-01-24 14:15:09 +0100trickard_trickard
2026-01-24 14:00:31 +0100trickard_(~trickard@cpe-93-98-47-163.wireline.com.au)
2026-01-24 14:00:17 +0100trickard_(~trickard@cpe-93-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2026-01-24 13:54:30 +0100Square2(~Square@user/square) (Ping timeout: 245 seconds)
2026-01-24 13:52:10 +0100Square3(~Square@user/square) Square
2026-01-24 13:41:50 +0100monochrom(trebla@216.138.220.146) monochrom
2026-01-24 13:29:49 +0100monochrom(trebla@216.138.220.146) (Ping timeout: 246 seconds)
2026-01-24 13:10:49 +0100michalz(~michalz@185.246.207.222)
2026-01-24 12:43:45 +0100chromoblob(~chromoblo@user/chromob1ot1c) chromoblob\0
2026-01-24 12:43:13 +0100chromoblob(~chromoblo@user/chromob1ot1c) (Ping timeout: 264 seconds)
2026-01-24 12:42:36 +0100GdeVolpiano(~GdeVolpia@user/GdeVolpiano) GdeVolpiano
2026-01-24 12:41:01 +0100GdeVolpi1(~GdeVolpia@user/GdeVolpiano) (Client Quit)
2026-01-24 12:39:50 +0100GdeVolpi1(~GdeVolpia@user/GdeVolpiano) GdeVolpiano
2026-01-24 12:39:45 +0100GdeVolpiano(~GdeVolpia@user/GdeVolpiano) (Read error: Connection reset by peer)
2026-01-24 12:20:40 +0100pavonia(~user@user/siracusa) siracusa
2026-01-24 12:16:24 +0100trickard_(~trickard@cpe-93-98-47-163.wireline.com.au)
2026-01-24 12:16:12 +0100068AAPXOS(~trickard@cpe-93-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2026-01-24 12:12:49 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) bitdex
2026-01-24 12:07:43 +0100__monty__(~toonn@user/toonn) toonn
2026-01-24 12:05:47 +0100Lycurgus(~juan@user/Lycurgus) (Quit: alsoknownas.renjuan.org ( juan@acm.org ))
2026-01-24 11:58:04 +0100 <c_wraith> then the typical package caching would be good enough.
2026-01-24 11:56:28 +0100 <c_wraith> What's really needed is a way to generate a freeze file that contains enough information that the cabal index is never touched.
2026-01-24 11:55:19 +0100pavonia(~user@user/siracusa) (Ping timeout: 240 seconds)
2026-01-24 11:52:52 +0100 <c_wraith> But tools to make it better don't really exist. caching the index doesn't help that much. Loading the cache takes about as much time as fetching it does.
2026-01-24 11:51:29 +0100 <c_wraith> just running cabal update takes like 30 seconds in github actions
2026-01-24 11:23:00 +0100Lycurgus(~juan@user/Lycurgus) Lycurgus
2026-01-24 11:07:38 +0100target_i(~target_i@user/target-i/x-6023099) target_i
2026-01-24 10:55:17 +0100 <sshine> can anyone recommend a simple replacement that gets cached more easily? context: https://github.com/sshine/evm-opcodes/blob/main/.github/workflows/haskell.yml#L30-L34
2026-01-24 10:54:29 +0100 <sshine> I have a GitHub Action haskell-actions/setup that takes 2m5s -- I'm wondering why this takes so long considering how actions/setup-java takes 0s.
2026-01-24 10:53:24 +0100sshine(~simon@dao.mechanicus.xyz) sshine
2026-01-24 10:46:31 +0100Square2(~Square@user/square) Square
2026-01-24 10:34:07 +0100vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 246 seconds)
2026-01-24 10:19:25 +0100wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2026-01-24 10:13:46 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Quit: Leaving...)
2026-01-24 10:09:40 +0100Sgeo(~Sgeo@user/sgeo) (Read error: Connection reset by peer)
2026-01-24 10:01:43 +0100peterbecich(~Thunderbi@71.84.33.135) (Ping timeout: 255 seconds)
2026-01-24 09:56:50 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-01-24 09:56:39 +0100vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2026-01-24 09:37:15 +0100skum(~skum@user/skum) (Quit: WeeChat 4.8.1)
2026-01-24 09:36:01 +0100hsw(~hsw@106.104.102.45) (Ping timeout: 264 seconds)
2026-01-24 09:30:07 +0100vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 250 seconds)
2026-01-24 09:20:19 +0100Tuplanolla(~Tuplanoll@85-156-32-207.elisa-laajakaista.fi) Tuplanolla
2026-01-24 09:11:55 +0100EvanR(~EvanR@user/evanr) EvanR
2026-01-24 09:11:35 +0100EvanR(~EvanR@user/evanr) (Remote host closed the connection)
2026-01-24 09:02:58 +0100vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2026-01-24 08:58:38 +0100monochrom(trebla@216.138.220.146) monochrom
2026-01-24 08:55:22 +0100 <gentauro> I would guess that VsCode should have a similar flow right?
2026-01-24 08:55:00 +0100 <gentauro> when I startup my project (in Emacs) I'm asked: `setup.hs is not part of any project.` and I usually choose: `i ==> Import project root /home/…/code/haskell/…/`
2026-01-24 08:53:58 +0100 <gentauro> like having a `setup.hs` in the `root` and then multiple `lib` and `exe`