2024/11/04

Newest at the top

2024-11-04 18:54:53 +0100 <briandaed> more core/threads would help?
2024-11-04 18:54:19 +0100 <sclv> i think its compute bound and suspect its just the hoogle code isn't super load efficient on some things
2024-11-04 18:53:45 +0100 <briandaed> sclv are these spam queries network(io) bound?
2024-11-04 18:44:28 +0100alp(~alp@2001:861:e3d6:8f80:8ee1:f46d:3f90:227c)
2024-11-04 18:31:39 +0100Digitteknohippie(~user@user/digit) Digit
2024-11-04 18:31:38 +0100Digit(~user@user/digit) (Ping timeout: 245 seconds)
2024-11-04 18:30:45 +0100LainExperiments(~LainExper@user/LainExperiments) LainExperiments
2024-11-04 18:18:25 +0100Leonard26(~Leonard26@49.236.10.26) (Quit: Client closed)
2024-11-04 18:17:29 +0100target_i(~target_i@user/target-i/x-6023099) (Quit: leaving)
2024-11-04 18:14:31 +0100Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) Tuplanolla
2024-11-04 18:08:12 +0100machinedgod(~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 244 seconds)
2024-11-04 18:01:12 +0100hiredman(~hiredman@frontier1.downey.family) hiredman
2024-11-04 18:00:55 +0100LainExperiments(~LainExper@user/LainExperiments) (Quit: Client closed)
2024-11-04 18:00:54 +0100morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 246 seconds)
2024-11-04 17:56:34 +0100morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-11-04 17:55:51 +0100 <sclv> what we need is a skilled admin to join us and help configure it to knock out the spam -- or maybe someone to work on making the code more efficient to handle load, or both :-)
2024-11-04 17:52:39 +0100comerijn(~merijn@77.242.116.146) (Ping timeout: 260 seconds)
2024-11-04 17:48:54 +0100spew(~spew@201.141.99.170) spew
2024-11-04 17:46:47 +0100 <haskellbridge> <hellwolf> or, we live with chances, which kinda worked too
2024-11-04 17:46:32 +0100 <haskellbridge> I think we can donate some money and setup a AWS WAF for it... shouldn't cost < $30 dollar
2024-11-04 17:46:32 +0100 <haskellbridge> <hellwolf> > It's apparently getting hit by a bunch of bot activity.
2024-11-04 17:44:44 +0100euphores(~SASL_euph@user/euphores) euphores
2024-11-04 17:43:54 +0100 <geekosaur> I haven't heard any complaints in the past week, so I guess it's back now?
2024-11-04 17:43:54 +0100 <dolio> It's apparently getting hit by a bunch of bot activity.
2024-11-04 17:43:26 +0100rvalue-rvalue
2024-11-04 17:41:52 +0100 <monochrom> Yeah hoogle was down some weeks ago.
2024-11-04 17:41:06 +0100 <haskellbridge> <hellwolf> Pardon me, I just recall it was hoogle instead.
2024-11-04 17:40:11 +0100monochromorganizes a water pistol party in the data centre!
2024-11-04 17:39:55 +0100ystael(~ystael@user/ystael) ystael
2024-11-04 17:39:23 +0100 <monochrom> But please don't pour water into computers!
2024-11-04 17:37:25 +0100 <geekosaur> (I'm putting out fires elsewhere…)
2024-11-04 17:37:21 +0100ystael(~ystael@user/ystael) (Quit: Lost terminal)
2024-11-04 17:37:17 +0100 <geekosaur> yay
2024-11-04 17:36:44 +0100rvalue(~rvalue@user/rvalue) (Ping timeout: 260 seconds)
2024-11-04 17:36:43 +0100euphores(~SASL_euph@user/euphores) (Quit: Leaving.)
2024-11-04 17:36:20 +0100 <sclv> also auto-status.haskell.org works again -- it needed some stuff reset
2024-11-04 17:35:56 +0100 <sclv> the only hackage downtime recently was an update on the 2nd and it does show that https://status.haskell.org/pages/maintenance/537c07b0cf1fad5830000093/67267208c5128b053d4b12c7
2024-11-04 17:35:38 +0100rvalue-(~rvalue@user/rvalue) rvalue
2024-11-04 17:35:08 +0100 <geekosaur> there used to be a live auto-status page but it seems to be gone
2024-11-04 17:34:57 +0100 <geekosaur> no, it's manual and if nobody reported it nobody will update it
2024-11-04 17:30:59 +0100euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de)
2024-11-04 17:30:17 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2024-11-04 17:30:09 +0100euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de) (Read error: Connection reset by peer)
2024-11-04 17:28:39 +0100ljdarj(~Thunderbi@user/ljdarj) ljdarj
2024-11-04 17:28:18 +0100 <haskellbridge> <hellwolf> Though the its history doesn't seem to show the hackage down times that I recently experienced.
2024-11-04 17:28:03 +0100euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de)
2024-11-04 17:27:19 +0100 <haskellbridge> <hellwolf> I didn't know there was a status.haskell.org page, thanks
2024-11-04 17:26:29 +0100 <statusbot6> Status update: Wiki.haskell.org is down due to an unsuccessful system upgrade. We are working on restoring service. -- http://status.haskell.org/pages/incident/537c07b0cf1fad5830000093/6728f5b530789205372a3361
2024-11-04 17:22:24 +0100alp(~alp@user/alp) (Ping timeout: 246 seconds)
2024-11-04 17:21:25 +0100Square(~Square@user/square) Square