2023/05/15

2023-05-15 00:00:00 +0200michalz(~michalz@185.246.207.200) (Remote host closed the connection)
2023-05-15 00:03:21 +0200Tuplanolla(~Tuplanoll@91-159-68-236.elisa-laajakaista.fi) (Ping timeout: 256 seconds)
2023-05-15 00:08:09 +0200acidjnk(~acidjnk@p200300d6e7072f04289ebaf0057e3058.dip0.t-ipconnect.de) (Ping timeout: 250 seconds)
2023-05-15 00:08:50 +0200ubert(~Thunderbi@p548c8bbe.dip0.t-ipconnect.de) (Quit: ubert)
2023-05-15 00:09:21 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 00:10:22 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net) (Ping timeout: 265 seconds)
2023-05-15 00:10:57 +0200monochrom(trebla@216.138.220.146) (Quit: NO CARRIER)
2023-05-15 00:14:13 +0200monochrom(trebla@216.138.220.146)
2023-05-15 00:14:14 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 265 seconds)
2023-05-15 00:15:42 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 00:18:17 +0200caryhartline(~caryhartl@107.140.218.181)
2023-05-15 00:20:00 +0200Pickchea(~private@user/pickchea) (Quit: Leaving)
2023-05-15 00:20:08 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 00:51:16 +0200pavonia(~user@user/siracusa)
2023-05-15 00:55:45 +0200caryhartline(~caryhartl@107.140.218.181) (Quit: caryhartline)
2023-05-15 00:57:37 +0200caryhartline(~caryhartl@2600:1700:2d0:8d30:a8ad:52bb:f68e:e718)
2023-05-15 00:59:15 +0200jle`(~jle`@cpe-23-240-75-236.socal.res.rr.com) (Ping timeout: 268 seconds)
2023-05-15 00:59:37 +0200paddymahoney(~paddymaho@cpe883d24bcf597-cmbc4dfb741f80.cpe.net.cable.rogers.com)
2023-05-15 01:01:02 +0200jle`(~jle`@cpe-23-240-75-236.socal.res.rr.com)
2023-05-15 01:01:45 +0200gurkenglas(~user@dynamic-046-114-176-178.46.114.pool.telefonica.de) (Ping timeout: 240 seconds)
2023-05-15 01:03:59 +0200gurkenglas(~user@dynamic-046-114-177-094.46.114.pool.telefonica.de)
2023-05-15 01:21:09 +0200mauke_(~mauke@user/mauke)
2023-05-15 01:23:18 +0200mauke(~mauke@user/mauke) (Ping timeout: 268 seconds)
2023-05-15 01:23:18 +0200mauke_mauke
2023-05-15 01:24:29 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:200b:a013:81d0:d721) (Remote host closed the connection)
2023-05-15 01:28:11 +0200gurkenglas(~user@dynamic-046-114-177-094.46.114.pool.telefonica.de) (Ping timeout: 265 seconds)
2023-05-15 01:30:26 +0200rf(~rf@2605:59c8:179c:f610:c307:c081:a3e:bb75)
2023-05-15 01:43:44 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 01:47:14 +0200kimjetwav(~user@2607:fea8:235e:b600:17dd:1c4:8522:e5d8)
2023-05-15 01:48:11 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 256 seconds)
2023-05-15 01:48:41 +0200oo_miguel(~Thunderbi@77.252.47.78) (Ping timeout: 246 seconds)
2023-05-15 01:57:20 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 02:01:35 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 02:11:12 +0200vandita(~vandit@87-97-13-47.pool.digikabel.hu) (Ping timeout: 265 seconds)
2023-05-15 02:12:36 +0200vandita(~vandit@94-21-33-124.pool.digikabel.hu)
2023-05-15 02:14:17 +0200wroathe(~wroathe@207-153-38-140.fttp.usinternet.com)
2023-05-15 02:14:18 +0200wroathe(~wroathe@207-153-38-140.fttp.usinternet.com) (Changing host)
2023-05-15 02:14:18 +0200wroathe(~wroathe@user/wroathe)
2023-05-15 02:18:08 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643) (Ping timeout: 240 seconds)
2023-05-15 02:21:13 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643)
2023-05-15 02:24:40 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 02:24:54 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:200b:a013:81d0:d721)
2023-05-15 02:29:08 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:200b:a013:81d0:d721) (Ping timeout: 240 seconds)
2023-05-15 02:29:11 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 02:31:37 +0200superbil(~superbil@1-34-176-171.hinet-ip.hinet.net) (Ping timeout: 258 seconds)
2023-05-15 02:41:14 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 02:42:35 +0200evincar(~evincar@user/evincar) (Ping timeout: 256 seconds)
2023-05-15 02:45:23 +0200evincar(~evincar@user/evincar)
2023-05-15 02:45:25 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 02:45:25 +0200nate2(~nate@98.45.169.16)
2023-05-15 02:45:35 +0200Fischmiep(~Fischmiep@user/Fischmiep) (Ping timeout: 240 seconds)
2023-05-15 02:54:59 +0200remexre(~remexre@user/remexre) (Remote host closed the connection)
2023-05-15 02:55:21 +0200remexre(~remexre@user/remexre)
2023-05-15 02:55:28 +0200remexre(~remexre@user/remexre) (Remote host closed the connection)
2023-05-15 02:55:46 +0200remexre(~remexre@user/remexre)
2023-05-15 02:56:48 +0200evincar(~evincar@user/evincar) (Ping timeout: 240 seconds)
2023-05-15 02:58:45 +0200remexre(~remexre@user/remexre) (Remote host closed the connection)
2023-05-15 02:59:05 +0200remexre(~remexre@user/remexre)
2023-05-15 02:59:19 +0200evincar(~evincar@user/evincar)
2023-05-15 03:02:46 +0200merijn(~merijn@86-86-29-250.fixed.kpn.net)
2023-05-15 03:03:00 +0200Fischmiep(~Fischmiep@user/Fischmiep)
2023-05-15 03:04:25 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 03:06:29 +0200Fischmiep(~Fischmiep@user/Fischmiep) (Excess Flood)
2023-05-15 03:07:00 +0200Fischmiep(~Fischmiep@user/Fischmiep)
2023-05-15 03:07:23 +0200merijn(~merijn@86-86-29-250.fixed.kpn.net) (Ping timeout: 264 seconds)
2023-05-15 03:08:47 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 03:10:50 +0200albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Remote host closed the connection)
2023-05-15 03:14:35 +0200evincar(~evincar@user/evincar) (Ping timeout: 264 seconds)
2023-05-15 03:16:57 +0200albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-05-15 03:19:57 +0200evincar(~evincar@user/evincar)
2023-05-15 03:22:59 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 03:23:06 +0200Feuermagier(~Feuermagi@user/feuermagier) (Quit: Leaving)
2023-05-15 03:23:31 +0200Feuermagier(~Feuermagi@user/feuermagier)
2023-05-15 03:28:54 +0200jscript(~jscript@cpe-172-193-181-254.qld.foxtel.net.au)
2023-05-15 03:30:28 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 03:36:57 +0200 <jscript> how do i get libgen to be found ?
2023-05-15 03:37:31 +0200evincar(~evincar@user/evincar) (Ping timeout: 240 seconds)
2023-05-15 03:38:38 +0200 <jscript> by ghc configure
2023-05-15 03:48:25 +0200nate2(~nate@98.45.169.16) (Ping timeout: 240 seconds)
2023-05-15 03:55:01 +0200[itchyjunk](~itchyjunk@user/itchyjunk/x-7353470) (Ping timeout: 240 seconds)
2023-05-15 03:56:02 +0200 <hololeap> library genesis?
2023-05-15 03:57:22 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 03:57:30 +0200 <jscript> yea
2023-05-15 03:57:40 +0200krei-se(~krei-se@p57af2733.dip0.t-ipconnect.de)
2023-05-15 03:57:41 +0200 <jscript> also llvm llc and llvm opt
2023-05-15 03:58:05 +0200 <jscript> and libtool
2023-05-15 03:59:48 +0200 <hololeap> jscript: how are you building ghc? I think there's options for hadrian to build via llvm
2023-05-15 04:00:05 +0200 <jscript> ./configure
2023-05-15 04:00:21 +0200 <jscript> for 8.6.1
2023-05-15 04:00:44 +0200[itchyjunk](~itchyjunk@user/itchyjunk/x-7353470)
2023-05-15 04:00:45 +0200 <hololeap> oh, that's super old... not sure how to help there
2023-05-15 04:02:04 +0200 <jscript> alright
2023-05-15 04:02:37 +0200 <hololeap> why are you trying to use such an old version?
2023-05-15 04:03:42 +0200 <jscript> for base .14
2023-05-15 04:03:43 +0200 <jscript> for base 1.14
2023-05-15 04:03:55 +0200 <jscript> [22:53] <dminuoso> HLS since published on hackage always demanded base >= 4.12 (which corresponds to GHC 8.6.1)
2023-05-15 04:04:08 +0200xff0x(~xff0x@2405:6580:b080:900:aeac:e4ca:6855:10e2) (Ping timeout: 246 seconds)
2023-05-15 04:05:24 +0200 <hololeap> released 2018-09-22
2023-05-15 04:05:56 +0200 <jscript> yea
2023-05-15 04:06:42 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net)
2023-05-15 04:07:57 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 268 seconds)
2023-05-15 04:09:08 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:200b:a013:81d0:d721)
2023-05-15 04:10:55 +0200 <hololeap> I personally wouldn't bother to test with such an old version, but I definitely wouldn't except using CI through github
2023-05-15 04:11:01 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net) (Ping timeout: 240 seconds)
2023-05-15 04:11:27 +0200 <hololeap> which uses debian and seems to "just work"
2023-05-15 04:11:33 +0200vandita(~vandit@94-21-33-124.pool.digikabel.hu) (Ping timeout: 265 seconds)
2023-05-15 04:11:53 +0200 <hololeap> or maybe ghcup would work, but I wouldn't be surprised if it doesn't go back that far
2023-05-15 04:12:18 +0200 <hololeap> 8.10? sure why not? 8.6? who is still using that??
2023-05-15 04:13:04 +0200 <hololeap> I think going back 3 major versions is plenty
2023-05-15 04:13:08 +0200vandita(~vandit@178-164-188-53.pool.digikabel.hu)
2023-05-15 04:13:29 +0200 <hololeap> e.g. 9.4, 9.2, 9.0 (maybe 8.10)
2023-05-15 04:14:44 +0200 <hololeap> haskell-language-server demands this?
2023-05-15 04:15:59 +0200td_(~td@i53870921.versanet.de) (Ping timeout: 240 seconds)
2023-05-15 04:16:18 +0200sympt(~sympt@user/sympt)
2023-05-15 04:18:06 +0200td_(~td@i5387092B.versanet.de)
2023-05-15 04:19:09 +0200 <probie> My last job was on 8.10.7 when I left (and I only left that at the start of this year). I think a fair few industry users will still be on 8.10
2023-05-15 04:24:13 +0200[itchyjunk](~itchyjunk@user/itchyjunk/x-7353470) (Remote host closed the connection)
2023-05-15 04:25:01 +0200nickhs(~nickhs@23.158.16.17)
2023-05-15 04:25:47 +0200 <nickhs> Hey there! i'm trying to use Aeson's eitherDecode to parse two different messages - similar to this https://play.haskell.org/saved/6vrKUnvz - but the compiler always picks the first branch for the type. Not sure how to best express that I want the type to be coerced?
2023-05-15 04:29:42 +0200caryhartline(~caryhartl@2600:1700:2d0:8d30:a8ad:52bb:f68e:e718) (Quit: caryhartline)
2023-05-15 04:33:13 +0200 <jackdk> $WORK is on 9.2.4 as another data point. I could imagine a performance-conscious GHCjs shop staying with 8.6.5
2023-05-15 04:37:12 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 04:39:56 +0200 <jackdk> nickhs: I don't think coercions are what you're looking for here. I would probably parse into a type that could represent either output that you seek. For example, defining a type `data Msg = Foo FooMsg | Bar BarMsg` and writing a `FromJSON` instance which attempts one parse and then the other. The `(<|>)` operator from class `Alternative` might be useful.
2023-05-15 04:41:35 +0200wroathe(~wroathe@user/wroathe) (Ping timeout: 264 seconds)
2023-05-15 04:42:10 +0200 <nickhs> jackdk: I think you're right, the "parse" here is a bad name since aesons actually already done the parsing/decoding - it's now up to two functions to process the message. I ended up creating a sum type to describe both cases and then unpacking and repacking the types inside each branch so the processFooMsg type can still only take in a foo msg
2023-05-15 04:42:15 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat)
2023-05-15 04:43:45 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::)
2023-05-15 04:45:33 +0200 <jackdk> Make sure you're not needlessly parsing the input string twice
2023-05-15 04:46:45 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 04:46:59 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 04:49:35 +0200mncheck(~mncheck@193.224.205.254) (Ping timeout: 240 seconds)
2023-05-15 04:51:38 +0200xff0x(~xff0x@125x103x176x34.ap125.ftth.ucom.ne.jp)
2023-05-15 04:58:45 +0200jscript(~jscript@cpe-172-193-181-254.qld.foxtel.net.au) (Quit: Konversation terminated!)
2023-05-15 04:58:56 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643) (Ping timeout: 240 seconds)
2023-05-15 05:01:22 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643)
2023-05-15 05:02:14 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 246 seconds)
2023-05-15 05:16:28 +0200nickhs(~nickhs@23.158.16.17) (Ping timeout: 245 seconds)
2023-05-15 05:17:05 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 05:20:40 +0200evincar(~evincar@user/evincar)
2023-05-15 05:21:47 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 264 seconds)
2023-05-15 05:23:52 +0200img(~img@user/img) (Quit: ZNC 1.8.2 - https://znc.in)
2023-05-15 05:24:40 +0200pharonix71(~pharonix7@user/pharonix71) (Remote host closed the connection)
2023-05-15 05:24:40 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643) (Read error: Connection reset by peer)
2023-05-15 05:24:40 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection)
2023-05-15 05:24:40 +0200califax(~califax@user/califx) (Write error: Connection reset by peer)
2023-05-15 05:24:40 +0200chexum(~quassel@gateway/tor-sasl/chexum) (Remote host closed the connection)
2023-05-15 05:24:55 +0200chexum(~quassel@gateway/tor-sasl/chexum)
2023-05-15 05:25:05 +0200califax(~califax@user/califx)
2023-05-15 05:25:06 +0200pharonix71(~pharonix7@user/pharonix71)
2023-05-15 05:25:14 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643)
2023-05-15 05:25:48 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex)
2023-05-15 05:28:55 +0200img(~img@user/img)
2023-05-15 05:39:51 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net)
2023-05-15 05:46:01 +0200rf(~rf@2605:59c8:179c:f610:c307:c081:a3e:bb75) (Ping timeout: 240 seconds)
2023-05-15 05:47:41 +0200titibandit(~titibandi@user/titibandit)
2023-05-15 05:48:28 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net) (Ping timeout: 268 seconds)
2023-05-15 05:49:56 +0200mixfix41(~sdeny9ee@user/mixfix41)
2023-05-15 06:01:29 +0200mixfix41(~sdeny9ee@user/mixfix41) (Quit: left libera)
2023-05-15 06:09:21 +0200_ht(~Thunderbi@28-52-174-82.ftth.glasoperator.nl)
2023-05-15 06:11:35 +0200titibandit(~titibandi@user/titibandit) (Ping timeout: 264 seconds)
2023-05-15 06:19:59 +0200vandita(~vandit@178-164-188-53.pool.digikabel.hu) (Ping timeout: 240 seconds)
2023-05-15 06:21:45 +0200vandita(~vandit@92-249-185-231.pool.digikabel.hu)
2023-05-15 06:24:13 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net)
2023-05-15 06:24:47 +0200evincar(~evincar@user/evincar) (Ping timeout: 240 seconds)
2023-05-15 06:25:09 +0200Guest71(~Guest71@178.232.104.138)
2023-05-15 06:28:07 +0200trev(~trev@user/trev)
2023-05-15 06:28:28 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net) (Ping timeout: 240 seconds)
2023-05-15 06:31:08 +0200img(~img@user/img) (Quit: ZNC 1.8.2 - https://znc.in)
2023-05-15 06:34:52 +0200monochrom(trebla@216.138.220.146) (Quit: NO CARRIER)
2023-05-15 06:36:04 +0200img(~img@user/img)
2023-05-15 06:40:59 +0200waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 264 seconds)
2023-05-15 06:53:35 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 06:57:07 +0200titibandit(~titibandi@user/titibandit)
2023-05-15 06:57:59 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 07:04:36 +0200takuan(~takuan@178-116-218-225.access.telenet.be)
2023-05-15 07:05:55 +0200takuan_dozo(~takuan@178-116-218-225.access.telenet.be)
2023-05-15 07:05:55 +0200takuan(~takuan@178-116-218-225.access.telenet.be) (Read error: Connection reset by peer)
2023-05-15 07:12:57 +0200mbuf(~Shakthi@49.207.178.186)
2023-05-15 07:18:25 +0200bgs(~bgs@212-85-160-171.dynamic.telemach.net)
2023-05-15 07:21:25 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 07:26:01 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 07:26:18 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net)
2023-05-15 07:31:08 +0200coot(~coot@89-69-206-216.dynamic.chello.pl)
2023-05-15 07:33:35 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net) (Ping timeout: 240 seconds)
2023-05-15 07:40:51 +0200evincar(~evincar@user/evincar)
2023-05-15 07:54:08 +0200boukenshaou(~Boukensha@115.248.21.178)
2023-05-15 07:55:00 +0200harveypwca(~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67)
2023-05-15 07:56:05 +0200boukenshaou(~Boukensha@115.248.21.178) (Client Quit)
2023-05-15 07:56:21 +0200boukenshaou(~Boukensha@115.248.21.178)
2023-05-15 07:59:46 +0200_ht(~Thunderbi@28-52-174-82.ftth.glasoperator.nl) (Remote host closed the connection)
2023-05-15 08:10:01 +0200bontaq(~user@ool-45779b84.dyn.optonline.net) (Ping timeout: 240 seconds)
2023-05-15 08:13:07 +0200monochrom(trebla@216.138.220.146)
2023-05-15 08:13:11 +0200vandita(~vandit@92-249-185-231.pool.digikabel.hu) (Ping timeout: 240 seconds)
2023-05-15 08:15:09 +0200vandita(~vandit@178-164-213-68.pool.digikabel.hu)
2023-05-15 08:19:44 +0200evincar(~evincar@user/evincar) (Ping timeout: 248 seconds)
2023-05-15 08:21:14 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 08:23:30 +0200titibandit(~titibandi@user/titibandit) (Remote host closed the connection)
2023-05-15 08:24:41 +0200titibandit(~titibandi@user/titibandit)
2023-05-15 08:28:11 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 268 seconds)
2023-05-15 08:29:20 +0200Taneb(~Taneb@2001:41c8:51:10d:aaaa:0:aaaa:0) (Ping timeout: 260 seconds)
2023-05-15 08:29:20 +0200landonf(landonf@mac68k.info) (Ping timeout: 260 seconds)
2023-05-15 08:29:20 +0200edm(sid147314@id-147314.hampstead.irccloud.com) (Ping timeout: 260 seconds)
2023-05-15 08:29:20 +0200supersven(sid501114@id-501114.ilkley.irccloud.com) (Ping timeout: 260 seconds)
2023-05-15 08:29:20 +0200bradparker(sid262931@id-262931.uxbridge.irccloud.com) (Ping timeout: 260 seconds)
2023-05-15 08:29:22 +0200qhong_(~qhong@DN160vrd000d6kpg009l6c0000fj.stanford.edu)
2023-05-15 08:29:25 +0200madnight(~madnight@static.59.103.201.195.clients.your-server.de) (Quit: ZNC 1.8.2 - https://znc.in)
2023-05-15 08:29:28 +0200supersven(sid501114@id-501114.ilkley.irccloud.com)
2023-05-15 08:29:31 +0200bradparker(sid262931@id-262931.uxbridge.irccloud.com)
2023-05-15 08:29:32 +0200landonf(landonf@mac68k.info)
2023-05-15 08:29:39 +0200madnight(~madnight@static.59.103.201.195.clients.your-server.de)
2023-05-15 08:29:40 +0200nshepperd21(nshepperd@2600:3c03::f03c:92ff:fe28:92c9)
2023-05-15 08:29:55 +0200qhong(~qhong@DN160vrd000d6kpg009l6c0000fj.stanford.edu) (Ping timeout: 260 seconds)
2023-05-15 08:29:55 +0200danso(~danso@user/danso) (Ping timeout: 260 seconds)
2023-05-15 08:29:55 +0200shawwwn(sid6132@id-6132.helmsley.irccloud.com) (Ping timeout: 260 seconds)
2023-05-15 08:29:55 +0200mht-wtf(~mht@2a03:b0c0:3:e0::1e2:c001) (Ping timeout: 260 seconds)
2023-05-15 08:29:55 +0200degraafk(sid71464@id-71464.lymington.irccloud.com) (Ping timeout: 260 seconds)
2023-05-15 08:29:55 +0200carter(sid14827@id-14827.helmsley.irccloud.com) (Ping timeout: 260 seconds)
2023-05-15 08:29:55 +0200Adeon(sid418992@id-418992.lymington.irccloud.com) (Ping timeout: 260 seconds)
2023-05-15 08:30:08 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 240 seconds)
2023-05-15 08:30:10 +0200Hobbyboy|BNC(Hobbyboy@hobbyboy.co.uk)
2023-05-15 08:30:11 +0200Dykam(Dykam@dykam.nl) (Remote host closed the connection)
2023-05-15 08:30:17 +0200anderson_(~ande@user/anderson)
2023-05-15 08:30:22 +0200kawen_(~quassel@static.208.191.216.95.clients.your-server.de) (Remote host closed the connection)
2023-05-15 08:30:30 +0200mtjm(~mutantmel@2604:a880:2:d0::208b:d001) (Ping timeout: 260 seconds)
2023-05-15 08:30:30 +0200meinside(uid24933@id-24933.helmsley.irccloud.com) (Ping timeout: 260 seconds)
2023-05-15 08:30:30 +0200Hobbyboy(Hobbyboy@hobbyboy.co.uk) (Ping timeout: 260 seconds)
2023-05-15 08:30:30 +0200Guest7839(sid22336@user/amir) (Ping timeout: 260 seconds)
2023-05-15 08:30:30 +0200S11001001(sid42510@id-42510.ilkley.irccloud.com) (Ping timeout: 260 seconds)
2023-05-15 08:30:30 +0200NemesisD(sid24071@id-24071.lymington.irccloud.com) (Ping timeout: 260 seconds)
2023-05-15 08:30:30 +0200beaky(~beaky@2a03:b0c0:0:1010::1e:a001) (Ping timeout: 260 seconds)
2023-05-15 08:30:34 +0200Taneb(~Taneb@2001:41c8:51:10d:aaaa:0:aaaa:0)
2023-05-15 08:30:39 +0200danso(~danso@user/danso)
2023-05-15 08:31:02 +0200CodeKiwi(~kiwi@2604:a880:400:d0::1ca0:e001)
2023-05-15 08:31:05 +0200heartburn(~gass@2a00:d880:3:1::b1e4:b241) (Ping timeout: 260 seconds)
2023-05-15 08:31:05 +0200fbytez(~uid@user/fbytez) (Ping timeout: 260 seconds)
2023-05-15 08:31:05 +0200DigitalKiwi(~kiwi@2604:a880:400:d0::1ca0:e001) (Ping timeout: 260 seconds)
2023-05-15 08:31:05 +0200anderson(~ande@user/anderson) (Ping timeout: 260 seconds)
2023-05-15 08:31:05 +0200dove(~irc@2600:3c00:e000:287::1) (Ping timeout: 260 seconds)
2023-05-15 08:31:05 +0200nshepperd2(nshepperd@2600:3c03::f03c:92ff:fe28:92c9) (Ping timeout: 260 seconds)
2023-05-15 08:31:05 +0200Hafydd(~Hafydd@user/hafydd) (Ping timeout: 260 seconds)
2023-05-15 08:31:05 +0200nshepperd(nshepperd@2600:3c03::f03c:92ff:fe28:92c9) (Ping timeout: 260 seconds)
2023-05-15 08:31:05 +0200christiaanb(sid84827@id-84827.lymington.irccloud.com) (Ping timeout: 260 seconds)
2023-05-15 08:31:05 +0200nshepperd21nshepperd2
2023-05-15 08:31:19 +0200Dykam(Dykam@dykam.nl)
2023-05-15 08:31:22 +0200fbytez(~uid@2001:bc8:2117:100::)
2023-05-15 08:31:30 +0200kawen(~quassel@static.208.191.216.95.clients.your-server.de)
2023-05-15 08:32:10 +0200beaky(~beaky@2a03:b0c0:0:1010::1e:a001)
2023-05-15 08:32:17 +0200NemesisD(sid24071@id-24071.lymington.irccloud.com)
2023-05-15 08:32:34 +0200Adeon(sid418992@id-418992.lymington.irccloud.com)
2023-05-15 08:32:47 +0200heartburn(~gass@2a00:d880:3:1::b1e4:b241)
2023-05-15 08:32:51 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex)
2023-05-15 08:32:54 +0200meinside(uid24933@id-24933.helmsley.irccloud.com)
2023-05-15 08:32:56 +0200degraafk(sid71464@id-71464.lymington.irccloud.com)
2023-05-15 08:32:57 +0200anderson_anderson
2023-05-15 08:32:58 +0200dove(~irc@2600:3c00:e000:287::1)
2023-05-15 08:33:03 +0200nshepperd(nshepperd@2600:3c03::f03c:92ff:fe28:92c9)
2023-05-15 08:33:07 +0200Guest7839(sid22336@id-22336.hampstead.irccloud.com)
2023-05-15 08:33:25 +0200carter(sid14827@id-14827.helmsley.irccloud.com)
2023-05-15 08:33:39 +0200christiaanb(sid84827@id-84827.lymington.irccloud.com)
2023-05-15 08:33:42 +0200acidjnk(~acidjnk@p200300d6e7072f49656669c7267a9e8d.dip0.t-ipconnect.de)
2023-05-15 08:33:55 +0200mtjm(~mutantmel@2604:a880:2:d0::208b:d001)
2023-05-15 08:34:33 +0200Hobbyboy|BNCHobbyboy
2023-05-15 08:35:38 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 08:36:03 +0200mht-wtf(~mht@2a03:b0c0:3:e0::1e2:c001)
2023-05-15 08:38:08 +0200azimut(~azimut@gateway/tor-sasl/azimut) (Ping timeout: 240 seconds)
2023-05-15 08:39:08 +0200mncheck(~mncheck@193.224.205.254)
2023-05-15 08:41:13 +0200potash(~potash@user/foghorn) (Ping timeout: 265 seconds)
2023-05-15 08:42:02 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 246 seconds)
2023-05-15 08:44:14 +0200edm_(sid147314@id-147314.hampstead.irccloud.com)
2023-05-15 08:44:41 +0200S11001001(sid42510@id-42510.ilkley.irccloud.com)
2023-05-15 08:44:57 +0200Hafydd(~Hafydd@user/hafydd)
2023-05-15 08:47:53 +0200shawwwn(sid6132@id-6132.helmsley.irccloud.com)
2023-05-15 08:50:50 +0200oo_miguel(~Thunderbi@77.252.47.78)
2023-05-15 08:52:02 +0200gmg(~user@user/gehmehgeh)
2023-05-15 08:55:39 +0200harveypwca(~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67) (Quit: Leaving)
2023-05-15 08:59:47 +0200Guest71(~Guest71@178.232.104.138) (Quit: Client closed)
2023-05-15 09:03:12 +0200merijn(~merijn@86-86-29-250.fixed.kpn.net)
2023-05-15 09:05:17 +0200evincar(~evincar@user/evincar)
2023-05-15 09:08:16 +0200merijn(~merijn@86-86-29-250.fixed.kpn.net) (Ping timeout: 268 seconds)
2023-05-15 09:09:01 +0200michalz(~michalz@185.246.207.203)
2023-05-15 09:09:56 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:f2f9:934b:840d:efc0)
2023-05-15 09:10:33 +0200titibandit(~titibandi@user/titibandit) (Remote host closed the connection)
2023-05-15 09:12:14 +0200gurkenglas(~user@dynamic-046-114-177-094.46.114.pool.telefonica.de)
2023-05-15 09:16:46 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 09:21:01 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 09:21:48 +0200titibandit(~titibandi@user/titibandit)
2023-05-15 09:30:04 +0200jero98772(~jero98772@2800:484:1d84:9000::2) (Ping timeout: 265 seconds)
2023-05-15 09:30:47 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 240 seconds)
2023-05-15 09:31:52 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-05-15 09:37:56 +0200ubert(~Thunderbi@p200300ecdf18b6bbcb3abf0ef164eaee.dip0.t-ipconnect.de)
2023-05-15 09:40:31 +0200Sgeo(~Sgeo@user/sgeo) (Read error: Connection reset by peer)
2023-05-15 09:41:18 +0200jero98772(~jero98772@2800:484:1d84:9000::2)
2023-05-15 09:46:31 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 09:50:56 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 248 seconds)
2023-05-15 09:57:07 +0200gmg(~user@user/gehmehgeh) (Quit: Leaving)
2023-05-15 09:58:39 +0200machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net)
2023-05-15 09:58:48 +0200evincar(~evincar@user/evincar) (Ping timeout: 240 seconds)
2023-05-15 10:03:29 +0200phma(~phma@host-67-44-208-35.hnremote.net) (Read error: Connection reset by peer)
2023-05-15 10:04:12 +0200phma(~phma@host-67-44-208-44.hnremote.net)
2023-05-15 10:05:12 +0200merijn(~merijn@185.143.104.11)
2023-05-15 10:05:35 +0200cheater(~Username@user/cheater) (Ping timeout: 264 seconds)
2023-05-15 10:14:13 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 256 seconds)
2023-05-15 10:15:30 +0200 <merijn> Anyone know how the monoidal behaviour of build-depends if you list the same dependency twice? does it union the version ranges? Use || or them? keep the last one?
2023-05-15 10:15:46 +0200 <merijn> (in cabal, ofc)
2023-05-15 10:15:48 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-05-15 10:17:36 +0200coot(~coot@89-69-206-216.dynamic.chello.pl) (Ping timeout: 248 seconds)
2023-05-15 10:18:24 +0200boukenshaou(~Boukensha@115.248.21.178) (Ping timeout: 265 seconds)
2023-05-15 10:19:18 +0200tzh(~tzh@c-24-21-73-154.hsd1.or.comcast.net) (Quit: zzz)
2023-05-15 10:19:39 +0200boukenshaou(~Boukensha@115.248.21.178)
2023-05-15 10:21:11 +0200chele(~chele@user/chele)
2023-05-15 10:21:37 +0200cfricke(~cfricke@user/cfricke)
2023-05-15 10:21:45 +0200vandita(~vandit@178-164-213-68.pool.digikabel.hu) (Ping timeout: 240 seconds)
2023-05-15 10:23:44 +0200vandita(~vandit@84-236-1-40.pool.digikabel.hu)
2023-05-15 10:25:40 +0200use-value(~Thunderbi@2a00:23c6:8a03:2f01:b0a5:d562:30d8:fcbb)
2023-05-15 10:26:58 +0200Angelz(Angelz@Angelz.oddprotocol.org) (Ping timeout: 250 seconds)
2023-05-15 10:28:06 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:200b:a013:81d0:d721) (Remote host closed the connection)
2023-05-15 10:32:31 +0200merijn(~merijn@185.143.104.11) (Ping timeout: 240 seconds)
2023-05-15 10:39:43 +0200jero98772(~jero98772@2800:484:1d84:9000::2) (Ping timeout: 256 seconds)
2023-05-15 10:42:28 +0200merijn(~merijn@185.143.104.11)
2023-05-15 10:43:15 +0200MelMalikAndreaB
2023-05-15 10:45:00 +0200Lord_of_Life_(~Lord@user/lord-of-life/x-2819915)
2023-05-15 10:45:11 +0200Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 240 seconds)
2023-05-15 10:46:18 +0200Lord_of_Life_Lord_of_Life
2023-05-15 10:46:46 +0200 <geekosaur> uses the last one, so you can override with a `--build-depends` or `cabal.project` etc., aiui
2023-05-15 10:47:57 +0200 <merijn> geekosaur: ok, that's probably the most useful behaviour for me, since I need some conditional blocks for differing compiler versions
2023-05-15 10:51:23 +0200jero98772(~jero98772@2800:484:1d84:9000::2)
2023-05-15 10:53:40 +0200nek0(~nek0@2a01:4f8:222:2b41::12) (Quit: The Lounge - https://thelounge.chat)
2023-05-15 10:53:54 +0200Angelz(Angelz@Angelz.oddprotocol.org)
2023-05-15 10:54:45 +0200 <c_wraith> yeah.. turns out cabal.project.freeze isn't special, except that it's loaded last of all the standard configs so that it can override less specific dependency bounds
2023-05-15 10:55:36 +0200tomsmedingwould have expected taking the intersection of the version ranges
2023-05-15 10:55:58 +0200 <tomsmeding> that would still allow overriding _less_ specific dependency bounds, but not _more_ specific ones
2023-05-15 10:56:21 +0200 <merijn> tomsmeding: But that's unhelpful with conditionals, though
2023-05-15 10:56:37 +0200 <c_wraith> in theory you could put other things cabal understands in cabal.project.freeze. Except that would surprise a lot of people and be really fragile as people tend to treat it as a file to delete and regenerate when needed.
2023-05-15 10:56:38 +0200 <merijn> tomsmeding: i.e. I might want two separate ranges for GHC 8.10 and 9.4
2023-05-15 10:56:49 +0200 <tomsmeding> merijn: I guess I would expect the conditionals to have an 'else' :p
2023-05-15 10:57:25 +0200 <tomsmeding> 'Last' is also defensible though
2023-05-15 10:57:54 +0200 <geekosaur> it's also easier 🙂
2023-05-15 10:58:04 +0200 <geekosaur> both to implement and to reason about
2023-05-15 10:58:15 +0200 <tomsmeding> is it? Wouldn't intersection just involve concatenating the lists of bounds
2023-05-15 10:58:32 +0200 <tomsmeding> and reasoning simplicity is subjective here :p
2023-05-15 10:59:20 +0200 <tomsmeding> i.e. can't I already write 'base >=4.14 >=4.15'
2023-05-15 10:59:32 +0200 <tomsmeding> well with && between them I guess
2023-05-15 11:01:59 +0200shriekingnoise(~shrieking@186.137.175.87) (Ping timeout: 240 seconds)
2023-05-15 11:02:36 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net)
2023-05-15 11:04:05 +0200kuribas(~user@ip-188-118-57-242.reverse.destiny.be)
2023-05-15 11:06:41 +0200nek0(~nek0@2a01:4f8:222:2b41::12)
2023-05-15 11:06:55 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net) (Ping timeout: 256 seconds)
2023-05-15 11:07:39 +0200zeenk(~zeenk@2a02:2f04:a105:f00::7fe)
2023-05-15 11:28:28 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:b97c:3991:b4ea:4289)
2023-05-15 11:32:01 +0200dontdieych(~alarm@132.226.169.184) (Quit: WeeChat 3.8)
2023-05-15 11:32:50 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:b97c:3991:b4ea:4289) (Ping timeout: 250 seconds)
2023-05-15 11:46:08 +0200ft(~ft@p4fc2a88b.dip0.t-ipconnect.de) (Quit: leaving)
2023-05-15 11:47:59 +0200mei(~mei@user/mei) (Ping timeout: 240 seconds)
2023-05-15 12:03:48 +0200jle`(~jle`@cpe-23-240-75-236.socal.res.rr.com) (Ping timeout: 240 seconds)
2023-05-15 12:04:32 +0200mei(~mei@user/mei)
2023-05-15 12:04:57 +0200ezzieyguywuf(~Unknown@user/ezzieyguywuf) (Ping timeout: 256 seconds)
2023-05-15 12:06:14 +0200jle`(~jle`@cpe-23-240-75-236.socal.res.rr.com)
2023-05-15 12:07:50 +0200xff0x(~xff0x@125x103x176x34.ap125.ftth.ucom.ne.jp) (Ping timeout: 246 seconds)
2023-05-15 12:09:26 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 12:11:38 +0200streetlamp(~Boukensha@115.248.21.178)
2023-05-15 12:13:39 +0200enoq(~enoq@2a05:1141:1f5:5600:b9c9:721a:599:bfe7)
2023-05-15 12:13:52 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 248 seconds)
2023-05-15 12:14:00 +0200boukenshaou(~Boukensha@115.248.21.178) (Ping timeout: 250 seconds)
2023-05-15 12:15:35 +0200ezzieyguywuf(~Unknown@user/ezzieyguywuf)
2023-05-15 12:16:19 +0200machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net) (Quit: Lost terminal)
2023-05-15 12:16:56 +0200machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net)
2023-05-15 12:20:06 +0200 <carbolymer> If I have a cabal library and executable, and a bit different version bounds in each one (tighter ones in executable), cabal will just pick a version satisfying both and use it bo build everything, right?
2023-05-15 12:23:39 +0200 <geekosaur> yes, presuming the executable depends on the library
2023-05-15 12:30:21 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:b97c:3991:b4ea:4289)
2023-05-15 12:31:20 +0200 <carbolymer> yes
2023-05-15 12:31:45 +0200 <carbolymer> so in this case, basically the version bound can be specified only in the library dependency
2023-05-15 12:32:18 +0200 <carbolymer> s/can be specified only/could be specified just
2023-05-15 12:33:27 +0200 <geekosaur> unless there's a reasonable case to be made for the library being usable without the executable, such that looser bounds make some sense
2023-05-15 12:34:48 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:b97c:3991:b4ea:4289) (Ping timeout: 250 seconds)
2023-05-15 12:46:06 +0200dontdieych(~alarm@132.226.169.184)
2023-05-15 12:50:03 +0200vandita(~vandit@84-236-1-40.pool.digikabel.hu) (Ping timeout: 256 seconds)
2023-05-15 12:51:39 +0200vandita(~vandit@178-164-207-107.pool.digikabel.hu)
2023-05-15 12:54:05 +0200zer0bitz_(~zer0bitz@user/zer0bitz)
2023-05-15 12:54:19 +0200CiaoSen(~Jura@dynamic-046-114-221-004.46.114.pool.telefonica.de)
2023-05-15 12:54:23 +0200jjb(~jjb@user/jjb) (Ping timeout: 240 seconds)
2023-05-15 12:55:09 +0200zer0bitz(~zer0bitz@user/zer0bitz) (Ping timeout: 256 seconds)
2023-05-15 12:55:15 +0200 <merijn> I think he means the executable depends on the library in the same package
2023-05-15 12:55:28 +0200 <merijn> In wich case, yes, you can leave the dependency on the executable unrestricted
2023-05-15 12:55:36 +0200 <merijn> Because the library will restrict it
2023-05-15 12:55:53 +0200 <carbolymer> yep, thanks geekosaur, merijn
2023-05-15 12:56:14 +0200 <merijn> tomsmeding: && would be silly, since that's just >=4.15 :p
2023-05-15 12:56:22 +0200 <merijn> tomsmeding: || or would make more sense
2023-05-15 12:56:37 +0200jjb(~jjb@user/jjb)
2023-05-15 12:56:55 +0200 <carbolymer> we have a situation now where version bounds are sprinkled everywhere, so simple dependency update triggers domino effect and necessity to change multiple packages
2023-05-15 13:02:34 +0200qhong_qhong
2023-05-15 13:03:49 +0200xff0x(~xff0x@ai098135.d.east.v6connect.net)
2023-05-15 13:10:51 +0200 <geekosaur[m]> merijn, but || is silly because that's just >= 4.14 :p
2023-05-15 13:13:00 +0200 <merijn> geekosaur[m]: ah, yeah, actually true :p
2023-05-15 13:13:44 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 13:18:05 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 13:18:45 +0200cfricke(~cfricke@user/cfricke) (Ping timeout: 240 seconds)
2023-05-15 13:26:45 +0200streetlamp(~Boukensha@115.248.21.178) (Remote host closed the connection)
2023-05-15 13:26:53 +0200gurkenglas(~user@dynamic-046-114-177-094.46.114.pool.telefonica.de) (Ping timeout: 256 seconds)
2023-05-15 13:31:01 +0200 <yin> in which situation would i want to limit a dependency's version?
2023-05-15 13:31:32 +0200 <yin> putting a ceiling on it, i mean
2023-05-15 13:31:38 +0200 <yin> an upper bound
2023-05-15 13:32:29 +0200 <yin> that'a not a major, breaking change
2023-05-15 13:34:42 +0200 <[exa]> yin: if you depend on specific behavior that dependency authors don't consider as breaking if modified
2023-05-15 13:35:38 +0200 <jade[m]> sometimes things like deprecations could get in your way
2023-05-15 13:36:24 +0200 <[exa]> "it slowed the program down by printing a gigaton of deprecation warnings" is a common engineering complaint, yes. :D
2023-05-15 13:36:57 +0200 <jade[m]> haha
2023-05-15 13:39:41 +0200 <[exa]> not funny, I had this happening in linux kernel, one networking patch started spewing a WARN for each packet that was sent to a network interface; which isn't helpful at all on a backbone router
2023-05-15 13:40:07 +0200gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c)
2023-05-15 13:42:04 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 13:42:12 +0200 <jade[m]> I thought you were joking 🤣
2023-05-15 13:42:30 +0200 <yin> that's amazing
2023-05-15 13:42:32 +0200 <[exa]> I wish I were
2023-05-15 13:42:49 +0200 <[exa]> anyway yeah events like this really adjust your attitude to dependency updates
2023-05-15 13:43:00 +0200 <yin> got it
2023-05-15 13:44:10 +0200 <[exa]> there's a pretty good approach with compathelpers nowadays, basically there's some automated thing (compathelper bot on github or so) that keeps dependencies upper bounds tight and scans for possible bumps when dependencies get released
2023-05-15 13:45:14 +0200 <[exa]> which is nice because 1] breakage won't sneak in 2] package is moreless up-to-date most of the time 3] because it's generating normal pull requests that trigger tests, the updates won't sneak around the tests
2023-05-15 13:45:38 +0200 <[exa]> but 4] if 2 packages somehow depend on each other and everything is automated, you get an infinite dependency bumping loop
2023-05-15 13:46:23 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 13:49:55 +0200 <yin> haskell should be an easy language to test for breaking changes
2023-05-15 13:50:10 +0200 <yin> i'm thinking edge cases and all that
2023-05-15 13:50:19 +0200 <yin> bottoms
2023-05-15 13:50:31 +0200akegalj(~akegalj@141-136-161-155.dsl.iskon.hr)
2023-05-15 13:50:46 +0200 <yin> it can provide at least some guarantees
2023-05-15 13:56:34 +0200akegalj(~akegalj@141-136-161-155.dsl.iskon.hr) (Quit: leaving)
2023-05-15 14:00:03 +0200 <geekosaur> until someone gets the bright idea of having a function you use ~constantly throw an exception in some cases, and then everything breaks silently
2023-05-15 14:00:13 +0200geekosaurstill miffed about that
2023-05-15 14:00:57 +0200 <yin> wait
2023-05-15 14:01:49 +0200 <yin> how can something throw an exception and break silently at the same time?
2023-05-15 14:02:17 +0200 <geekosaur> "break at runtime instead of throwing a compile error because you violated a new invariant"
2023-05-15 14:03:21 +0200geekosaurargued for it being `Maybe` or `ExceptT` and lost. then we got two separate waves of user-reported crashes
2023-05-15 14:03:39 +0200 <yin> ia this a popular module?
2023-05-15 14:04:15 +0200 <geekosaur> X11, as of a couple years ago. xmonad uses `getWindowAttributes` from it
2023-05-15 14:04:36 +0200 <yin> ouch, that sounds awful
2023-05-15 14:04:46 +0200 <geekosaur> arguably it was a bugfix because the function would silently produce garbage (but usually not a coredump)
2023-05-15 14:05:01 +0200 <geekosaur> but it shouldn't habve changed to an exception because those can't be typechecked
2023-05-15 14:05:21 +0200 <geekosaur> and every use suddenly had to be wrapped in `catch`, `catchX`, or `userCode`
2023-05-15 14:05:38 +0200 <geekosaur> (the latter two being xmonad internal handler functions)
2023-05-15 14:15:32 +0200vglfr(~vglfr@2a0d:3344:1b4f:9e10:add0:f322:8c39:7887)
2023-05-15 14:16:36 +0200vglfr(~vglfr@2a0d:3344:1b4f:9e10:add0:f322:8c39:7887) (Remote host closed the connection)
2023-05-15 14:17:10 +0200vglfr(~vglfr@2a0d:3344:1b4f:9e10:add0:f322:8c39:7887)
2023-05-15 14:17:12 +0200vglfr(~vglfr@2a0d:3344:1b4f:9e10:add0:f322:8c39:7887) (Remote host closed the connection)
2023-05-15 14:18:57 +0200vglfr(~vglfr@2a0d:3344:1b4f:9e10:add0:f322:8c39:7887)
2023-05-15 14:19:18 +0200vglfr(~vglfr@2a0d:3344:1b4f:9e10:add0:f322:8c39:7887) (Remote host closed the connection)
2023-05-15 14:20:15 +0200vglfr(~vglfr@2a0d:3344:1b4f:9e10:add0:f322:8c39:7887)
2023-05-15 14:25:22 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Quit: = "")
2023-05-15 14:26:50 +0200freeside_(~mengwong@103.252.202.151)
2023-05-15 14:28:23 +0200freeside1(~mengwong@185.223.152.159)
2023-05-15 14:28:45 +0200 <dminuoso> Is there some newtype wrappers that have a memoized hash of the thing inside for faster comparison?
2023-05-15 14:30:25 +0200 <geekosaur> er? by runtime there's no "inside"
2023-05-15 14:30:50 +0200 <dminuoso> Oh, I guess `data` :-)
2023-05-15 14:31:16 +0200 <dminuoso> My brain just imagined everything I could possibly desire to be free.
2023-05-15 14:31:23 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 264 seconds)
2023-05-15 14:33:24 +0200chomwitt(~chomwitt@2a02:587:7a04:2000:1ac0:4dff:fedb:a3f1)
2023-05-15 14:33:40 +0200 <yin> dminuoso: can't you use somekind of Map?
2023-05-15 14:33:42 +0200 <geekosaur> might this be a use case for a StablePtr?
2023-05-15 14:34:52 +0200 <dminuoso> Mmm, StablePtr wont work (imagine you have a bytestring that was copied)
2023-05-15 14:35:12 +0200freeside_(~mengwong@103.252.202.151) (Ping timeout: 248 seconds)
2023-05-15 14:35:37 +0200 <dminuoso> But I guess Ill just cook myself some TextWithHash
2023-05-15 14:45:37 +0200cfricke(~cfricke@user/cfricke)
2023-05-15 14:48:21 +0200 <merijn> :O
2023-05-15 14:48:38 +0200 <merijn> Wait, Hackage has built in notifications for when your dependencies are updated out of your bounds? :O
2023-05-15 14:56:00 +0200ub(~Thunderbi@p200300ecdf18b6bbfb0914264665628c.dip0.t-ipconnect.de)
2023-05-15 14:59:30 +0200 <merijn> geekosaur[m], tomsmeding: I'm sad to report version constraints are, in fact, && together
2023-05-15 15:00:57 +0200 <merijn> Well, that sucks balls
2023-05-15 15:01:40 +0200 <merijn> That's gonna make it way more annoying to write this all out
2023-05-15 15:02:53 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net)
2023-05-15 15:06:26 +0200 <dminuoso> carbolymer: One thing to keep in mind, that obviously there is not going to be a "perfect" plan. So if if the executable component introduces extra constraints it can leave with some bizarre artifacts (because cabal-plan will not do an exhaustive search)
2023-05-15 15:07:08 +0200wiosna(~karangura@c-73-93-95-154.hsd1.ca.comcast.net) (Ping timeout: 240 seconds)
2023-05-15 15:07:49 +0200 <dminuoso> Though in reality this will be rare (since generally lower versions will broadly have lower upper bounds on its dependencies)
2023-05-15 15:08:23 +0200vandita(~vandit@178-164-207-107.pool.digikabel.hu) (Ping timeout: 240 seconds)
2023-05-15 15:09:23 +0200 <Hecate> dminuoso: FastString in GHC ?
2023-05-15 15:09:43 +0200 <dminuoso> Hecate: Ohh!
2023-05-15 15:09:54 +0200cheater(~Username@user/cheater)
2023-05-15 15:10:03 +0200 <merijn> bleh
2023-05-15 15:10:23 +0200vandita(~vandit@92-249-179-105.pool.digikabel.hu)
2023-05-15 15:10:24 +0200 <merijn> And I can't write a single version in build-depends with an || modifier
2023-05-15 15:10:27 +0200 <dminuoso> Hecate: Yes! I need to plug that out :)
2023-05-15 15:10:39 +0200 <merijn> bah
2023-05-15 15:11:02 +0200 <dminuoso> merijn: with the intent to communicate that if that constraint is inherited (via a transitive dependency), its ORed and not ANDed?
2023-05-15 15:11:29 +0200 <merijn> dminuoso: Not transitive
2023-05-15 15:11:55 +0200 <Hecate> dminuoso: 👍 :)
2023-05-15 15:11:58 +0200 <merijn> Basically, I have a dependency on "mtl ^>= 2.3.1" and I wanted to selectively override that with 2.2.2 for GHC 9.0
2023-05-15 15:12:01 +0200 <carbolymer> dminuoso: by bizarre artifacts you mean unbuildable plan?
2023-05-15 15:12:11 +0200 <dminuoso> carbolymer: Not necessarily.
2023-05-15 15:12:31 +0200 <dminuoso> carbolymer: cabal-plan does not do an exhaustive search of all plans.
2023-05-15 15:12:37 +0200 <merijn> dminuoso: I don't want to generalise the entire buildplan on other GHCs to allow 2.2.2 though
2023-05-15 15:13:19 +0200enoq(~enoq@2a05:1141:1f5:5600:b9c9:721a:599:bfe7) (Quit: enoq)
2023-05-15 15:13:20 +0200 <merijn> So I just wanted "mtl ^>= 2.3.1" 'if impl(ghc == 9.0.*) build-depends: mtl ^>= 2.2.2"
2023-05-15 15:13:28 +0200 <dminuoso> carbolymer: or rather, if a buildable plan exists (with the specified flags), cabal-plan will find it
2023-05-15 15:13:40 +0200 <dminuoso> But it is not guaranteed to give you the "best plan" (whatever that means)
2023-05-15 15:13:47 +0200 <merijn> But now I need to write if/else, moving mtl out of the overall dependency list
2023-05-15 15:14:02 +0200 <merijn> And I need to do that for a number of other dependencies, which is kinda annoying
2023-05-15 15:18:04 +0200chomwitt(~chomwitt@2a02:587:7a04:2000:1ac0:4dff:fedb:a3f1) (Remote host closed the connection)
2023-05-15 15:26:57 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 15:30:36 +0200cfricke(~cfricke@user/cfricke) (Ping timeout: 268 seconds)
2023-05-15 15:30:56 +0200[itchyjunk](~itchyjunk@user/itchyjunk/x-7353470)
2023-05-15 15:32:17 +0200merijn(~merijn@185.143.104.11) (Read error: Connection reset by peer)
2023-05-15 15:32:26 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:b97c:3991:b4ea:4289)
2023-05-15 15:32:35 +0200merijn(~merijn@c-001-001-015.client.esciencecenter.eduvpn.nl)
2023-05-15 15:34:24 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 248 seconds)
2023-05-15 15:36:47 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:b97c:3991:b4ea:4289) (Ping timeout: 246 seconds)
2023-05-15 15:39:23 +0200brettgilio(~brettgili@x-irc.gq)
2023-05-15 15:52:15 +0200L29Ah(~L29Ah@wikipedia/L29Ah) ()
2023-05-15 15:52:33 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2023-05-15 15:55:40 +0200gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) (Quit: WeeChat 3.8)
2023-05-15 15:58:33 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 15:59:16 +0200CodeKiwiDigitalKiwi
2023-05-15 16:07:01 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 16:15:45 +0200ub(~Thunderbi@p200300ecdf18b6bbfb0914264665628c.dip0.t-ipconnect.de) (Ping timeout: 256 seconds)
2023-05-15 16:16:05 +0200ub(~Thunderbi@p200300ecdf18b6bbfb0914264665628c.dip0.t-ipconnect.de)
2023-05-15 16:19:25 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 16:20:48 +0200waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7)
2023-05-15 16:22:23 +0200oo_miguel(~Thunderbi@77.252.47.78) (Ping timeout: 240 seconds)
2023-05-15 16:24:20 +0200chexum(~quassel@gateway/tor-sasl/chexum) (Quit: No Ping reply in 180 seconds.)
2023-05-15 16:24:45 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 16:25:41 +0200chexum(~quassel@gateway/tor-sasl/chexum)
2023-05-15 16:35:04 +0200oo_miguel(~Thunderbi@77.252.47.78)
2023-05-15 16:35:08 +0200nick4(~nick@wsip-174-78-110-18.pn.at.cox.net)
2023-05-15 16:35:31 +0200Sgeo(~Sgeo@user/sgeo)
2023-05-15 16:37:11 +0200shriekingnoise(~shrieking@186.137.175.87)
2023-05-15 16:48:00 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 16:55:25 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 256 seconds)
2023-05-15 17:11:17 +0200merijn(~merijn@c-001-001-015.client.esciencecenter.eduvpn.nl) (Ping timeout: 246 seconds)
2023-05-15 17:11:40 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 17:12:23 +0200ub1(~Thunderbi@p548c8bbe.dip0.t-ipconnect.de)
2023-05-15 17:12:35 +0200ub(~Thunderbi@p200300ecdf18b6bbfb0914264665628c.dip0.t-ipconnect.de) (Remote host closed the connection)
2023-05-15 17:14:40 +0200ub1ub
2023-05-15 17:15:20 +0200merijn(~merijn@c-001-001-015.client.esciencecenter.eduvpn.nl)
2023-05-15 17:18:02 +0200viwor(~Thunderbi@IGLD-83-130-212-68.inter.net.il)
2023-05-15 17:18:12 +0200xff0x(~xff0x@ai098135.d.east.v6connect.net) (Ping timeout: 250 seconds)
2023-05-15 17:19:48 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 17:20:09 +0200xff0x(~xff0x@178.255.149.135)
2023-05-15 17:22:00 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection)
2023-05-15 17:23:45 +0200azimut(~azimut@gateway/tor-sasl/azimut)
2023-05-15 17:25:18 +0200xff0x(~xff0x@178.255.149.135) (Ping timeout: 268 seconds)
2023-05-15 17:26:25 +0200xff0x(~xff0x@ai098135.d.east.v6connect.net)
2023-05-15 17:27:02 +0200eggplantade(~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net)
2023-05-15 17:28:26 +0200acidjnk(~acidjnk@p200300d6e7072f49656669c7267a9e8d.dip0.t-ipconnect.de) (Ping timeout: 246 seconds)
2023-05-15 17:28:28 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 17:31:55 +0200_ht(~Thunderbi@28-52-174-82.ftth.glasoperator.nl)
2023-05-15 17:32:03 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:f2f9:934b:840d:efc0) (Quit: WeeChat 2.8)
2023-05-15 17:32:45 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 17:32:59 +0200finsternis(~X@23.226.237.192) (Ping timeout: 248 seconds)
2023-05-15 17:34:22 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 17:36:57 +0200pavonia(~user@user/siracusa) (Quit: Bye!)
2023-05-15 17:40:45 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 17:44:24 +0200merijn(~merijn@c-001-001-015.client.esciencecenter.eduvpn.nl) (Quit: leaving)
2023-05-15 17:44:48 +0200ubert(~Thunderbi@p200300ecdf18b6bbcb3abf0ef164eaee.dip0.t-ipconnect.de) (Ping timeout: 240 seconds)
2023-05-15 17:44:48 +0200ububert
2023-05-15 17:44:51 +0200albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Remote host closed the connection)
2023-05-15 17:47:32 +0200Sciencentistguy4(~sciencent@hacksoc/ordinary-member)
2023-05-15 17:49:23 +0200cheater(~Username@user/cheater) (Ping timeout: 264 seconds)
2023-05-15 17:49:59 +0200Sciencentistguy(~sciencent@hacksoc/ordinary-member) (Ping timeout: 240 seconds)
2023-05-15 17:49:59 +0200Sciencentistguy4Sciencentistguy
2023-05-15 17:50:59 +0200albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-05-15 17:51:49 +0200nick4(~nick@wsip-174-78-110-18.pn.at.cox.net) (Ping timeout: 268 seconds)
2023-05-15 18:00:00 +0200cheater(~Username@user/cheater)
2023-05-15 18:03:28 +0200gurkenglas(~user@dynamic-046-114-177-094.46.114.pool.telefonica.de)
2023-05-15 18:04:46 +0200kuribas(~user@ip-188-118-57-242.reverse.destiny.be) (Remote host closed the connection)
2023-05-15 18:05:24 +0200foghorn(~foghorn@user/foghorn) (Remote host closed the connection)
2023-05-15 18:07:24 +0200econo(uid147250@user/econo)
2023-05-15 18:08:32 +0200CiaoSen(~Jura@dynamic-046-114-221-004.46.114.pool.telefonica.de) (Ping timeout: 248 seconds)
2023-05-15 18:08:59 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 18:09:36 +0200machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net) (Ping timeout: 248 seconds)
2023-05-15 18:11:37 +0200tzh(~tzh@c-24-21-73-154.hsd1.wa.comcast.net)
2023-05-15 18:11:55 +0200out-of-memory(~out-of-me@172.58.160.241)
2023-05-15 18:12:46 +0200 <out-of-memory> Hello! I have a program that is exiting with "out of memory", but when I compile with profiling enabled, it works fine!
2023-05-15 18:12:59 +0200 <out-of-memory> Does anyone have any rough pointers for a case like this?
2023-05-15 18:13:05 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 18:13:20 +0200waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 248 seconds)
2023-05-15 18:13:50 +0200 <out-of-memory> The numbers look totally reasonable in profiling mode
2023-05-15 18:14:05 +0200 <out-of-memory> Not too much allocation, not too much GC
2023-05-15 18:15:22 +0200 <out-of-memory> I am using GHC.Compact, so I probably have 40 or 60 separate regions. That comes out to (60 * 32kb = 1920kb) so less than 2mb of pinned memory from that.
2023-05-15 18:17:16 +0200 <geekosaur> you could try building with -O0 since profiling disables optimization, but that's less than ideal for practical use
2023-05-15 18:17:53 +0200 <geekosaur> also if it says something about being unable to mmap 4096 bytes at nil, you may be hitting a recent linux kernel bug
2023-05-15 18:18:34 +0200 <out-of-memory> I'll try to do -O0 without profiling and see what happens. Be right back!
2023-05-15 18:20:04 +0200 <out-of-memory> I actually have a question about that though. In my .cabal file: I have a line like this:
2023-05-15 18:20:04 +0200 <out-of-memory> ghc-options: -threaded -O0 -Wall -Werror
2023-05-15 18:20:05 +0200 <out-of-memory> But in the output while it is rebuilding, it says "Build profile: -w ghc-9.4.4 -O1"
2023-05-15 18:20:43 +0200 <out-of-memory> I have noticed this before, but I didn't care quite enough to look into it more. It seems to choose -O1 regardless of whether I say -O0 or -O2 in my cabal file.
2023-05-15 18:21:18 +0200 <sclv> yeah the profile is the top level settings
2023-05-15 18:21:33 +0200 <sclv> the cabal file takes precidence
2023-05-15 18:21:49 +0200 <sclv> the profile applies to all deps as well etc
2023-05-15 18:22:03 +0200 <johnw> hi sclv!
2023-05-15 18:22:32 +0200 <sclv> hi john, long time!!
2023-05-15 18:24:09 +0200 <johnw> yes, very long time
2023-05-15 18:24:22 +0200 <johnw> I'm coming to NYC next week, but I'll only be at Rockaway Beach
2023-05-15 18:24:54 +0200 <sclv> ah drat. would have been nice to say hi
2023-05-15 18:25:37 +0200 <geekosaur> if you're forcing -O0 you may be missing out on optimizations that will reduce memory usage, although I'd more expect that to cause more garbage collections rather than complain about out of memory
2023-05-15 18:25:44 +0200 <geekosaur> are you setting a cap on the heap?
2023-05-15 18:25:53 +0200 <geekosaur> (RTS option)
2023-05-15 18:26:36 +0200 <out-of-memory> No cap, I am letting it pretty much do the defaults.
2023-05-15 18:26:43 +0200 <out-of-memory> I only have "ghc-options: -threaded -O0 -Wall -Werror" listed
2023-05-15 18:26:55 +0200 <out-of-memory> when I call the binary, I say "+RTS -N"
2023-05-15 18:27:13 +0200 <out-of-memory> It's still a work in progress, so I haven't tried to do any tuning of RTS variables
2023-05-15 18:27:41 +0200 <out-of-memory> I'll show the output of -s to get an idea of things. One sec.
2023-05-15 18:29:35 +0200 <out-of-memory> sclv, I looked at the top level settings (in `~/.cabal/config` for 3.6 it seems) and it does not explicitly set an optimization level. I assume that means O1 is just the default?
2023-05-15 18:29:35 +0200vandita(~vandit@92-249-179-105.pool.digikabel.hu) (Ping timeout: 264 seconds)
2023-05-15 18:29:52 +0200 <sclv> yep
2023-05-15 18:30:38 +0200 <out-of-memory> Is there a way to confirm which -O flag which used for a specific build?
2023-05-15 18:31:08 +0200vandita(~vandit@94-21-55-53.pool.digikabel.hu)
2023-05-15 18:31:25 +0200 <out-of-memory> Here's the -s output: https://paste.tomsmeding.com/gwxMCGbt
2023-05-15 18:32:54 +0200 <out-of-memory> My program is a compiler. It is compiling around 20 files. The weirdest features I use are probably GHC.Compact and GHC.Prim structures.
2023-05-15 18:33:55 +0200 <out-of-memory> I don't have any C calls in my code though
2023-05-15 18:34:18 +0200 <out-of-memory> So from -s, it seems like everything is fine, but I turn off profiling and get the "out of memory" again
2023-05-15 18:34:38 +0200 <out-of-memory> Can it be something lazy that is getting forced infinitely?
2023-05-15 18:35:01 +0200 <geekosaur> profiling shouldn't affect that
2023-05-15 18:35:09 +0200 <out-of-memory> (It also gives "out of memory" very very quickly. I'm not seeing a spike in my OS view of memory usage either.)
2023-05-15 18:36:12 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 18:36:14 +0200 <out-of-memory> Could strictness analysis trigger that though? (I have never looked into strictness analysis enough to know if this could happen.)
2023-05-15 18:36:48 +0200 <geekosaur> I would expect profiling changing strictness analysis to be a bug
2023-05-15 18:37:08 +0200 <out-of-memory> Okay, that's a good reference point!
2023-05-15 18:37:13 +0200gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c)
2023-05-15 18:37:30 +0200 <geekosaur> it's bad enough that profiling disables optimization (we recently got -fprof-late to help with that)
2023-05-15 18:38:02 +0200 <out-of-memory> I'll look into what that flag does. Maybe it'll help me get the "out of memory" while profiling is on?
2023-05-15 18:38:20 +0200euandreh(~Thunderbi@189.6.18.7) (Read error: Connection reset by peer)
2023-05-15 18:38:21 +0200 <geekosaur> it might,m but I think you need to be on 9.6.1 to get that flag
2023-05-15 18:38:31 +0200titibandit(~titibandi@user/titibandit) (Remote host closed the connection)
2023-05-15 18:39:21 +0200szkl(uid110435@id-110435.uxbridge.irccloud.com)
2023-05-15 18:39:53 +0200 <out-of-memory> It says since 9.4.1 here https://downloads.haskell.org/ghc/latest/docs/users_guide/profiling.html#ghc-flag--fprof-late and it's compiling at the moment. Will find out how it goes soon!
2023-05-15 18:40:24 +0200 <out-of-memory> Thank you for helping me through this by the way!
2023-05-15 18:41:06 +0200 <geekosaur> no problem, that's what we're here for
2023-05-15 18:41:21 +0200 <out-of-memory> This flag seems like a great addition! Excited to try it out seriously once this project is ready for optimization :)
2023-05-15 18:41:44 +0200 <geekosaur> seriously? I'd optimize up front
2023-05-15 18:43:41 +0200 <out-of-memory> In my particular case, I need to get a working implementation before I put too much focus on optimization.
2023-05-15 18:43:44 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 248 seconds)
2023-05-15 18:44:04 +0200 <out-of-memory> I've been working on this program basically for ~10 years, so I know where the odd spots are by now.
2023-05-15 18:44:35 +0200 <geekosaur> optimizing the code you write is one thing, letting the compiler do optimizations is another. -O0 is basically debugging the compiler 🙂
2023-05-15 18:44:38 +0200 <out-of-memory> Okay, no "out of memory" when using the -fprof-late flag!
2023-05-15 18:45:18 +0200jjb(~jjb@user/jjb) (Ping timeout: 250 seconds)
2023-05-15 18:45:25 +0200mbuf(~Shakthi@49.207.178.186) (Quit: Leaving)
2023-05-15 18:45:32 +0200 <geekosaur> now that's interesting. might be worth a bug report, although testing with 9.4.5 might be warranted first
2023-05-15 18:46:03 +0200 <out-of-memory> Ah, I am on 9.4.4. I'll check out the release notes real quick.
2023-05-15 18:46:43 +0200 <out-of-memory> Is there a way to absolutely confirm which flags were used for a given executable?
2023-05-15 18:47:01 +0200 <c_wraith> Sometimes I wish GHC did fewer optimizations that serve to fix strictness errors and the like. My theory is that would make people a lot less shocked when programs get complex enough that those optimizations no longer fix all their oversights.
2023-05-15 18:47:01 +0200 <geekosaur> not that I'm aware of. sclv might know more
2023-05-15 18:47:04 +0200jjb(~jjb@user/jjb)
2023-05-15 18:48:43 +0200euandreh(~Thunderbi@189.6.18.7)
2023-05-15 18:49:02 +0200 <geekosaur> huuuh. looks like gcc embeds compile options in its code. maybe that should be proposed for ghc
2023-05-15 18:49:39 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 18:49:40 +0200 <sclv> this sounds like a compiler bug possibly. i remember there were some issues where things went funny on boxes with LOTs of memory because it overflowed ghc's own limits
2023-05-15 18:49:54 +0200 <sclv> so explicitly running with heap and stack sizes set sufficiently large may help
2023-05-15 18:50:16 +0200 <sclv> (in particular if a box had enough memory, ghc would calculate a very small default heap size due to an integer overflow)
2023-05-15 18:50:47 +0200 <sclv> those should well be resolved by the 9.4.4 compiler, but who knows
2023-05-15 18:50:52 +0200czy(~user@host-140-24.ilcub310.champaign.il.us.clients.pavlovmedia.net)
2023-05-15 18:51:02 +0200 <geekosaur> I would also expect that to not be affected by profiling
2023-05-15 18:51:39 +0200 <out-of-memory> Interesting! I'll play around with setting heap and stack sizes. (I am on a 2013 MacBook Air, but it'd be good to see if the particular line where the failure occurs changes dramatically.)
2023-05-15 18:51:51 +0200 <out-of-memory> The 9.4.5 notes don't say anything that looks relevent https://downloads.haskell.org/~ghc/9.4.5/docs/users_guide/9.4.5-notes.html#runtime-system
2023-05-15 18:52:30 +0200 <out-of-memory> So it may be getting a small heap and stack because it's pretty old, haha
2023-05-15 18:52:37 +0200 <out-of-memory> I'll report back soon!
2023-05-15 18:52:55 +0200chele(~chele@user/chele) (Remote host closed the connection)
2023-05-15 18:53:48 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 18:54:30 +0200 <sclv> no way afaik to extract ghc flags a binary was compiled with. the cabal-hash file for each package in the store does provide the cleartext of the cabal hash, but that stores the _cabal level_ flags.
2023-05-15 18:56:01 +0200 <out-of-memory> I started recording SHA for each executable produced, so I can at least confirm that they are different.
2023-05-15 18:59:12 +0200zeenk(~zeenk@2a02:2f04:a105:f00::7fe) (Quit: Konversation terminated!)
2023-05-15 19:00:57 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 19:08:00 +0200 <out-of-memory> I am seeing different hashes for executables with different flags. I am still investigating different RTS flags though. (It's a lot of files, so compiles are kind of slow.)
2023-05-15 19:08:13 +0200 <out-of-memory> (For confirming the hashes I mean)
2023-05-15 19:08:25 +0200 <geekosaur> yes, but they're hashes so you can't reconstruct the flags from the hashes
2023-05-15 19:11:23 +0200 <out-of-memory> I at least know the executable is changing based on changing -O0 to -O1 to -O2 which at least detects "I am at optimization level I didn't expect"
2023-05-15 19:12:02 +0200 <out-of-memory> I cannot reproduce the out-of-memory anymore. All I have been doing is messing with flags in a .cabal file. Very weird.
2023-05-15 19:12:36 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 268 seconds)
2023-05-15 19:13:02 +0200 <out-of-memory> Using "ghc-options: -threaded -O1 -Wall -Werror -rtsopts" now and it's gone.
2023-05-15 19:13:40 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 19:14:00 +0200 <out-of-memory> I am pretty baffled by how this could happen, so I'll keep an eye out in case it comes up again.
2023-05-15 19:15:15 +0200 <out-of-memory> In any case, thank you so much geekosaur and sclv for helping me through this problem! Very happy to be able to continue with regular optimization flags, even if it is mysterious why haha
2023-05-15 19:15:21 +0200 <geekosaur> might still be worth reporting although trying it with `+RTS -M8G` or something might be revealing
2023-05-15 19:15:41 +0200 <out-of-memory> I can try that. One sec
2023-05-15 19:15:51 +0200 <out-of-memory> (I don't think I have that much RAM, haha)
2023-05-15 19:15:52 +0200 <geekosaur> that's a runtime option, not a compile option
2023-05-15 19:16:07 +0200 <geekosaur> oh, hm
2023-05-15 19:16:12 +0200 <out-of-memory> Yeah, it worked fine!
2023-05-15 19:16:47 +0200 <geekosaur> okay, so the RTS may be setting the heap size funny
2023-05-15 19:17:45 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 19:19:31 +0200 <out-of-memory> I think making a reproducible version of this will be pretty hard. (Have 199 modules at the moment!) But I'll cross that bridge if I come to it! Thank you again!
2023-05-15 19:20:03 +0200 <geekosaur> np
2023-05-15 19:26:29 +0200shinjipf(~shinjipf@137.184.4.49) (Quit: Shinji leaves)
2023-05-15 19:26:55 +0200shinjipf(~shinjipf@137.184.4.49)
2023-05-15 19:27:07 +0200oats_(~thomas@user/oats)
2023-05-15 19:28:48 +0200oats_tomas
2023-05-15 19:34:48 +0200out-of-memory(~out-of-me@172.58.160.241) (Ping timeout: 245 seconds)
2023-05-15 19:41:38 +0200cheater(~Username@user/cheater) (Ping timeout: 250 seconds)
2023-05-15 19:47:35 +0200Sgeo(~Sgeo@user/sgeo) (Ping timeout: 264 seconds)
2023-05-15 19:48:17 +0200czy(~user@host-140-24.ilcub310.champaign.il.us.clients.pavlovmedia.net) (Remote host closed the connection)
2023-05-15 19:53:04 +0200vglfr(~vglfr@2a0d:3344:1b4f:9e10:add0:f322:8c39:7887) (Ping timeout: 248 seconds)
2023-05-15 19:53:16 +0200vglfr(~vglfr@209.198.137.226)
2023-05-15 19:55:35 +0200oo_miguel(~Thunderbi@77.252.47.78) (Ping timeout: 240 seconds)
2023-05-15 20:06:25 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 20:08:59 +0200Tuplanolla(~Tuplanoll@91-159-68-236.elisa-laajakaista.fi)
2023-05-15 20:10:55 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 256 seconds)
2023-05-15 20:13:09 +0200Feuermagier(~Feuermagi@user/feuermagier) (Remote host closed the connection)
2023-05-15 20:13:50 +0200waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7)
2023-05-15 20:15:35 +0200euandreh(~Thunderbi@189.6.18.7) (Remote host closed the connection)
2023-05-15 20:15:58 +0200euandreh(~Thunderbi@189.6.18.7)
2023-05-15 20:25:46 +0200coot(~coot@89-69-206-216.dynamic.chello.pl)
2023-05-15 20:36:23 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 20:43:33 +0200zer0bitz_(~zer0bitz@user/zer0bitz) (Quit: No Ping reply in 180 seconds.)
2023-05-15 20:44:10 +0200szkl(uid110435@id-110435.uxbridge.irccloud.com) (Quit: Connection closed for inactivity)
2023-05-15 20:44:47 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 20:45:00 +0200zer0bitz(~zer0bitz@user/zer0bitz)
2023-05-15 20:45:59 +0200mei(~mei@user/mei) (Remote host closed the connection)
2023-05-15 20:46:14 +0200coot(~coot@89-69-206-216.dynamic.chello.pl) (Quit: coot)
2023-05-15 20:46:45 +0200rf(~rf@142.99.241.242)
2023-05-15 20:51:26 +0200simendsjo(~user@84.211.91.241)
2023-05-15 20:52:44 +0200simendsjo(~user@84.211.91.241) (Remote host closed the connection)
2023-05-15 20:53:46 +0200mei(~mei@user/mei)
2023-05-15 20:58:38 +0200vulpine(xfnw@tilde.team) (Quit: Connection reset by purr)
2023-05-15 20:59:52 +0200vulpine(xfnw@tilde.team)
2023-05-15 21:02:03 +0200vglfr(~vglfr@209.198.137.226) (Read error: Connection reset by peer)
2023-05-15 21:02:15 +0200vglfr(~vglfr@2a0d:3344:1b4f:9e10:5c0a:60fc:aa33:b5d6)
2023-05-15 21:07:15 +0200zer0bitz(~zer0bitz@user/zer0bitz) (Quit: No Ping reply in 180 seconds.)
2023-05-15 21:08:41 +0200zer0bitz(~zer0bitz@user/zer0bitz)
2023-05-15 21:10:00 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 21:10:58 +0200oo_miguel(~Thunderbi@77.252.47.78)
2023-05-15 21:11:02 +0200machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net)
2023-05-15 21:11:45 +0200mechap(~mechap@user/mechap) (Quit: WeeChat 3.8)
2023-05-15 21:11:46 +0200Sgeo(~Sgeo@user/sgeo)
2023-05-15 21:14:35 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 264 seconds)
2023-05-15 21:23:57 +0200vglfr(~vglfr@2a0d:3344:1b4f:9e10:5c0a:60fc:aa33:b5d6) (Ping timeout: 265 seconds)
2023-05-15 21:24:56 +0200vglfr(~vglfr@209.198.137.226)
2023-05-15 21:25:26 +0200vglfr(~vglfr@209.198.137.226) (Read error: Connection reset by peer)
2023-05-15 21:25:41 +0200vglfr(~vglfr@209.198.137.226)
2023-05-15 21:27:06 +0200rf_(~rf@142.99.241.246)
2023-05-15 21:27:59 +0200vglfr(~vglfr@209.198.137.226) (Read error: Connection reset by peer)
2023-05-15 21:28:01 +0200rf(~rf@142.99.241.242) (Ping timeout: 240 seconds)
2023-05-15 21:28:11 +0200vglfr(~vglfr@209.198.137.226)
2023-05-15 21:30:31 +0200vglfr(~vglfr@209.198.137.226) (Read error: Connection reset by peer)
2023-05-15 21:30:46 +0200vglfr(~vglfr@209.198.137.226)
2023-05-15 21:31:05 +0200gurkenglas(~user@dynamic-046-114-177-094.46.114.pool.telefonica.de) (Ping timeout: 240 seconds)
2023-05-15 21:31:15 +0200pavonia(~user@user/siracusa)
2023-05-15 21:32:23 +0200ft(~ft@p4fc2a88b.dip0.t-ipconnect.de)
2023-05-15 21:33:46 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 21:34:10 +0200user____1(~user@dynamic-046-114-177-094.46.114.pool.telefonica.de)
2023-05-15 21:35:08 +0200user____1gurkenglas
2023-05-15 21:37:20 +0200eggplantade(~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net) (Remote host closed the connection)
2023-05-15 21:37:59 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 21:39:47 +0200heartburn(~gass@2a00:d880:3:1::b1e4:b241) (Ping timeout: 264 seconds)
2023-05-15 21:40:49 +0200mechap(~mechap@user/mechap)
2023-05-15 21:45:16 +0200mmhat(~mmh@p200300f1c70668f7ee086bfffe095315.dip0.t-ipconnect.de)
2023-05-15 21:45:46 +0200acidjnk(~acidjnk@p200300d6e7072f49e923159d5e1d01b5.dip0.t-ipconnect.de)
2023-05-15 21:47:40 +0200heartburn(~gass@2a00:d880:3:1::b1e4:b241)
2023-05-15 21:50:31 +0200vglfr(~vglfr@209.198.137.226) (Read error: Connection reset by peer)
2023-05-15 21:55:19 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 21:58:41 +0200vglfr(~vglfr@209.198.137.226)
2023-05-15 21:59:35 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 22:02:31 +0200cheater(~Username@user/cheater)
2023-05-15 22:03:07 +0200vglfr(~vglfr@209.198.137.226) (Ping timeout: 256 seconds)
2023-05-15 22:03:45 +0200vglfr(~vglfr@209.198.137.226)
2023-05-15 22:04:37 +0200mechap(~mechap@user/mechap) (Quit: WeeChat 3.8)
2023-05-15 22:05:42 +0200mechap(~mechap@user/mechap)
2023-05-15 22:06:47 +0200_ht(~Thunderbi@28-52-174-82.ftth.glasoperator.nl) (Quit: _ht)
2023-05-15 22:06:54 +0200dr_merijn(~merijn@c-001-001-015.client.esciencecenter.eduvpn.nl)
2023-05-15 22:07:18 +0200dr_merijnmerijn
2023-05-15 22:08:03 +0200 <merijn> bleh
2023-05-15 22:08:08 +0200 <merijn> asum is in Prelude now?
2023-05-15 22:08:28 +0200 <merijn> So how do I import it in a backwards compatible manner without GHC bitching at me about unused imports?
2023-05-15 22:09:00 +0200 <merijn> And of course no mention of this in the migration guide...
2023-05-15 22:10:21 +0200 <merijn> Am I stuck with CPP to silence this? Because that's gonna annoy me if that's the case
2023-05-15 22:12:01 +0200mechap(~mechap@user/mechap) (Quit: WeeChat 3.8)
2023-05-15 22:18:21 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 22:18:40 +0200vandita(~vandit@94-21-55-53.pool.digikabel.hu) (Ping timeout: 248 seconds)
2023-05-15 22:20:24 +0200vandita(~vandit@188-143-101-93.pool.digikabel.hu)
2023-05-15 22:22:59 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 264 seconds)
2023-05-15 22:25:23 +0200rf_(~rf@142.99.241.246) (Quit: Leaving)
2023-05-15 22:25:42 +0200rf(~rf@142.99.241.246)
2023-05-15 22:27:59 +0200merijn(~merijn@c-001-001-015.client.esciencecenter.eduvpn.nl) (Ping timeout: 240 seconds)
2023-05-15 22:36:08 +0200takuan_dozo(~takuan@178-116-218-225.access.telenet.be) (Ping timeout: 240 seconds)
2023-05-15 22:37:46 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:b97c:3991:b4ea:4289)
2023-05-15 22:37:48 +0200trev(~trev@user/trev) (Quit: trev)
2023-05-15 22:38:40 +0200 <sm> merijn: I'm not seeing the context, so ignore if off the mark, but the *-compat packages have been helpful with this kind of thing
2023-05-15 22:42:20 +0200eggplantade(~Eggplanta@2600:1700:38c5:d800:b97c:3991:b4ea:4289) (Ping timeout: 250 seconds)
2023-05-15 22:43:01 +0200tan00kee(~paul@pauloliver.dev)
2023-05-15 22:44:58 +0200Pickchea(~private@user/pickchea)
2023-05-15 22:45:48 +0200evincar(~evincar@user/evincar)
2023-05-15 22:50:29 +0200monix(~quassel@a85-138-255-115.cpe.netcabo.pt)
2023-05-15 22:55:00 +0200merijn(~merijn@c-001-001-015.client.esciencecenter.eduvpn.nl)
2023-05-15 22:56:24 +0200coot(~coot@89-69-206-216.dynamic.chello.pl)
2023-05-15 22:58:05 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 23:01:22 +0200Lycurgus(~juan@user/Lycurgus)
2023-05-15 23:02:37 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 268 seconds)
2023-05-15 23:04:06 +0200bgs(~bgs@212-85-160-171.dynamic.telemach.net) (Remote host closed the connection)
2023-05-15 23:07:37 +0200coot(~coot@89-69-206-216.dynamic.chello.pl) (Quit: coot)
2023-05-15 23:20:34 +0200emmanuelux(~emmanuelu@user/emmanuelux) (Quit: au revoir)
2023-05-15 23:23:17 +0200zeenk(~zeenk@2a02:2f04:a105:f00::7fe)
2023-05-15 23:24:09 +0200cheater(~Username@user/cheater) (Ping timeout: 256 seconds)
2023-05-15 23:24:17 +0200freeside(~mengwong@103.252.202.151)
2023-05-15 23:26:04 +0200zer0bitz_(~zer0bitz@user/zer0bitz)
2023-05-15 23:27:19 +0200eL_Bart0-(eL_Bart0@dietunichtguten.org)
2023-05-15 23:27:28 +0200eL_Bart0(eL_Bart0@dietunichtguten.org) (Ping timeout: 248 seconds)
2023-05-15 23:27:31 +0200buhman_(sid411355@user/buhman) (Ping timeout: 240 seconds)
2023-05-15 23:27:31 +0200lally(sid388228@id-388228.uxbridge.irccloud.com) (Ping timeout: 240 seconds)
2023-05-15 23:27:31 +0200potato44(uid421314@id-421314.lymington.irccloud.com) (Ping timeout: 240 seconds)
2023-05-15 23:27:31 +0200filwisher(2e6936c793@2604:bf00:561:2000::170) (Ping timeout: 240 seconds)
2023-05-15 23:27:41 +0200lally(sid388228@id-388228.uxbridge.irccloud.com)
2023-05-15 23:28:01 +0200Vajb(~Vajb@2001:999:489:9fc7:2a48:2fed:ac18:a255) (Ping timeout: 240 seconds)
2023-05-15 23:28:01 +0200gonz________(sid304396@id-304396.lymington.irccloud.com) (Ping timeout: 240 seconds)
2023-05-15 23:28:01 +0200alinab_(sid468903@id-468903.helmsley.irccloud.com) (Ping timeout: 240 seconds)
2023-05-15 23:28:01 +0200lexi-lambda(sid92601@id-92601.hampstead.irccloud.com) (Ping timeout: 240 seconds)
2023-05-15 23:28:23 +0200merijn(~merijn@c-001-001-015.client.esciencecenter.eduvpn.nl) (Ping timeout: 264 seconds)
2023-05-15 23:28:25 +0200freeside(~mengwong@103.252.202.151) (Ping timeout: 240 seconds)
2023-05-15 23:28:31 +0200Kamuela_(sid111576@id-111576.tinside.irccloud.com) (Ping timeout: 240 seconds)
2023-05-15 23:28:31 +0200integral(sid296274@user/integral) (Ping timeout: 240 seconds)
2023-05-15 23:28:31 +0200mustafa_(sid502723@rockylinux/releng/mustafa) (Ping timeout: 240 seconds)
2023-05-15 23:28:31 +0200dmj`(sid72307@id-72307.hampstead.irccloud.com) (Ping timeout: 240 seconds)
2023-05-15 23:28:31 +0200shreyasminocha(51fdc93eda@user/shreyasminocha) (Ping timeout: 240 seconds)
2023-05-15 23:28:31 +0200samhh(7569f027cf@2604:bf00:561:2000::e4) (Ping timeout: 240 seconds)
2023-05-15 23:28:34 +0200jil(~user@vps-15050500.vps.ovh.net) (Read error: Connection reset by peer)
2023-05-15 23:29:01 +0200zer0bitz(~zer0bitz@user/zer0bitz) (Ping timeout: 240 seconds)
2023-05-15 23:29:01 +0200nek0(~nek0@2a01:4f8:222:2b41::12) (Ping timeout: 240 seconds)
2023-05-15 23:29:01 +0200Angelz(Angelz@Angelz.oddprotocol.org) (Ping timeout: 240 seconds)
2023-05-15 23:29:01 +0200Hafydd(~Hafydd@user/hafydd) (Ping timeout: 240 seconds)
2023-05-15 23:29:01 +0200tcard(~tcard@2400:4051:5801:7500:cf17:befc:ff82:5303) (Ping timeout: 240 seconds)
2023-05-15 23:29:01 +0200glowcoil(sid3405@id-3405.tinside.irccloud.com) (Ping timeout: 240 seconds)
2023-05-15 23:29:01 +0200cpli(77fc530071@2604:bf00:561:2000::252) (Ping timeout: 240 seconds)
2023-05-15 23:29:11 +0200potato44(uid421314@2a03:5180:f:2::6:6dc2)
2023-05-15 23:29:18 +0200zeenk(~zeenk@2a02:2f04:a105:f00::7fe) (Remote host closed the connection)
2023-05-15 23:29:26 +0200alinab_(sid468903@id-468903.helmsley.irccloud.com)
2023-05-15 23:29:31 +0200mira(~aranea@wireguard/contributorcat/mira) (Ping timeout: 240 seconds)
2023-05-15 23:29:33 +0200tcard_(~tcard@2400:4051:5801:7500:cf17:befc:ff82:5303)
2023-05-15 23:29:33 +0200nek06(~nek0@2a01:4f8:222:2b41::12)
2023-05-15 23:29:33 +0200jil`(~user@vps-15050500.vps.ovh.net)
2023-05-15 23:29:40 +0200zeenk2(~zeenk@2a02:2f04:a105:f00::7fe)
2023-05-15 23:29:46 +0200integral(sid296274@user/integral)
2023-05-15 23:29:46 +0200mustafa__(sid502723@id-502723.hampstead.irccloud.com)
2023-05-15 23:29:49 +0200gonz________(sid304396@id-304396.lymington.irccloud.com)
2023-05-15 23:29:49 +0200buhman_(sid411355@id-411355.tinside.irccloud.com)
2023-05-15 23:29:51 +0200Hafydd(~Hafydd@user/hafydd)
2023-05-15 23:29:53 +0200Kamuela__(sid111576@id-111576.tinside.irccloud.com)
2023-05-15 23:30:01 +0200rf(~rf@142.99.241.246) (Ping timeout: 240 seconds)
2023-05-15 23:30:21 +0200filwisher_(2e6936c793@2604:bf00:561:2000::170)
2023-05-15 23:30:22 +0200shreyasminocha(51fdc93eda@user/shreyasminocha)
2023-05-15 23:30:24 +0200mira(~aranea@wireguard/contributorcat/mira)
2023-05-15 23:30:26 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Quit: Leaving)
2023-05-15 23:31:00 +0200michalz(~michalz@185.246.207.203) (Remote host closed the connection)
2023-05-15 23:31:06 +0200nek06nek0
2023-05-15 23:31:06 +0200Kamuela__Kamuela_
2023-05-15 23:31:45 +0200glowcoil(sid3405@id-3405.tinside.irccloud.com)
2023-05-15 23:31:59 +0200dmj`(sid72307@id-72307.hampstead.irccloud.com)
2023-05-15 23:32:29 +0200gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) (Quit: WeeChat 3.8)
2023-05-15 23:34:16 +0200samhh(7569f027cf@2604:bf00:561:2000::e4)
2023-05-15 23:38:33 +0200cpli(77fc530071@2604:bf00:561:2000::252)
2023-05-15 23:41:01 +0200cheater(~Username@user/cheater)
2023-05-15 23:41:18 +0200oo_miguel(~Thunderbi@77.252.47.78) (Quit: oo_miguel)
2023-05-15 23:41:21 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2023-05-15 23:41:43 +0200oo_miguel(~Thunderbi@77.252.47.78)
2023-05-15 23:41:50 +0200lexi-lambda(sid92601@id-92601.hampstead.irccloud.com)
2023-05-15 23:42:15 +0200merijn(~merijn@c-001-001-015.client.esciencecenter.eduvpn.nl)
2023-05-15 23:45:24 +0200Angelz(Angelz@angelz.oddprotocol.org)
2023-05-15 23:48:15 +0200merijn(~merijn@c-001-001-015.client.esciencecenter.eduvpn.nl) (Ping timeout: 268 seconds)
2023-05-15 23:53:35 +0200Tuplanolla(~Tuplanoll@91-159-68-236.elisa-laajakaista.fi) (Ping timeout: 240 seconds)
2023-05-15 23:56:08 +0200vandita(~vandit@188-143-101-93.pool.digikabel.hu) (Read error: Connection reset by peer)
2023-05-15 23:59:31 +0200vandita(~vandit@94-21-108-18.pool.digikabel.hu)