Newest at the top
| 2024-11-06 19:40:52 +0100 | <haskellbridge> | <sm> unless it was very quick :) but seems unlikely |
| 2024-11-06 19:40:21 +0100 | <haskellbridge> | <sm> no |
| 2024-11-06 19:40:12 +0100 | krei-se | (~krei-se@p5085d46e.dip0.t-ipconnect.de) (Read error: Connection reset by peer) |
| 2024-11-06 19:39:56 +0100 | <haskellbridge> | <Morj> Not according to the website, huh |
| 2024-11-06 19:39:38 +0100 | <haskellbridge> | <Morj> Did stackage also go down just now? |
| 2024-11-06 19:39:22 +0100 | Tuplanolla | (~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) Tuplanolla |
| 2024-11-06 19:38:18 +0100 | jco | (~jco@78-70-217-44-no600.tbcn.telia.com) (Ping timeout: 252 seconds) |
| 2024-11-06 19:34:23 +0100 | <briandaed> | had no time to dig deeper, tested on virtualized fedora with four cores and 6gigs of ram |
| 2024-11-06 19:33:35 +0100 | <sm> | any such optimising is valuable |
| 2024-11-06 19:33:19 +0100 | krei-se | (~krei-se@p5085d46e.dip0.t-ipconnect.de) krei-se |
| 2024-11-06 19:33:13 +0100 | <sm> | briandaed nice |
| 2024-11-06 19:32:27 +0100 | <sm> | I set up https://haskell-status.joyful.com today, which updates quicker |
| 2024-11-06 19:31:32 +0100 | <geekosaur> | and apparently a lot of other internet services are being affected as well |
| 2024-11-06 19:31:22 +0100 | <briandaed> | I spend some time testing why hoogle is so slow, build it from sources and made requests same as sclv has shown us, it was spending 58% of the time calculatin inRanges https://github.com/ndmitchell/hoogle/blob/master/src/General/Util.hs#L359 |
| 2024-11-06 19:30:49 +0100 | krei-se | (~krei-se@p5085d46e.dip0.t-ipconnect.de) (Read error: Connection reset by peer) |
| 2024-11-06 19:30:15 +0100 | pie_ | (~pie_bnc@user/pie/x-2818909) __ |
| 2024-11-06 19:29:15 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 276 seconds) |
| 2024-11-06 19:28:19 +0100 | <geekosaur> | that was only activated yesterday, it remains to be seen how much it's contributing because the bot spam had been going on for weeks (it's largely why hoogle was down a lot, apparently) |
| 2024-11-06 19:27:07 +0100 | <briandaed> | like geekosaur said, it's probably an effect of 'bot fighting' functionality from cloudflare, sclv and chreekat can shed some light.. |
| 2024-11-06 19:26:27 +0100 | <jco> | I see, thanks... |
| 2024-11-06 19:24:51 +0100 | <institor> | maybe the app server is overloaded |
| 2024-11-06 19:24:42 +0100 | <institor> | that would explain the intermittent behavior |
| 2024-11-06 19:23:53 +0100 | <geekosaur> | and ignoring things like robots.txt |
| 2024-11-06 19:23:44 +0100 | <geekosaur> | from what I've seen, it seems like a lot of AI crawlers have been hammering hackage and hoogle |
| 2024-11-06 19:23:13 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 248 seconds) |
| 2024-11-06 19:22:36 +0100 | <jco> | Hey, what's up with https://hackage.haskell.org? Get 503s and it feels like that site has been having problems for a while. https://status.haskell.org seems to indicate there's an ongoing incident. Does anyone here know more about this? |
| 2024-11-06 19:19:59 +0100 | wootehfoot | (~wootehfoo@user/wootehfoot) wootehfoot |
| 2024-11-06 19:17:54 +0100 | jco | (~jco@78-70-217-44-no600.tbcn.telia.com) jco |
| 2024-11-06 19:07:32 +0100 | <statusbot6> | Status update: there is a network outage affecting hackage, we are investigating -- http://status.haskell.org/pages/incident/537c07b0cf1fad5830000093/672bb063281978053cb3d85e |
| 2024-11-06 19:01:58 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2024-11-06 18:57:28 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 245 seconds) |
| 2024-11-06 18:35:16 +0100 | briandaed | (~root@185.234.210.211.r.toneticgroup.pl) |
| 2024-11-06 18:31:36 +0100 | kuribas | (~user@ip-188-118-57-242.reverse.destiny.be) (Remote host closed the connection) |
| 2024-11-06 18:29:48 +0100 | ljdarj1 | ljdarj |
| 2024-11-06 18:29:48 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 244 seconds) |
| 2024-11-06 18:27:32 +0100 | ljdarj1 | (~Thunderbi@user/ljdarj) ljdarj |
| 2024-11-06 18:19:18 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2024-11-06 18:13:52 +0100 | pabs3 | (~pabs3@user/pabs3) pabs3 |
| 2024-11-06 18:10:46 +0100 | jrm | (~jrm@user/jrm) jrm |
| 2024-11-06 18:09:57 +0100 | Guest7 | (~Guest7@syn-172-249-181-078.res.spectrum.com) (Ping timeout: 256 seconds) |
| 2024-11-06 18:09:17 +0100 | jrm | (~jrm@user/jrm) (Quit: ciao) |
| 2024-11-06 18:00:51 +0100 | pabs3 | (~pabs3@user/pabs3) (Ping timeout: 276 seconds) |
| 2024-11-06 17:51:57 +0100 | sprotte24 | (~sprotte24@p200300d16f45f600c5ad94218b2aa1c2.dip0.t-ipconnect.de) (Quit: Leaving) |
| 2024-11-06 17:48:16 +0100 | euleritian | (~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de) |
| 2024-11-06 17:48:01 +0100 | euleritian | (~euleritia@dynamic-176-007-150-185.176.7.pool.telefonica.de) (Read error: Connection reset by peer) |
| 2024-11-06 17:47:08 +0100 | son0p | (~ff@186.119.84.155) son0p |
| 2024-11-06 17:44:48 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 265 seconds) |
| 2024-11-06 17:44:48 +0100 | chele | (~chele@user/chele) (Remote host closed the connection) |
| 2024-11-06 17:38:46 +0100 | Smiles | (uid551636@id-551636.lymington.irccloud.com) (Quit: Connection closed for inactivity) |
| 2024-11-06 17:33:27 +0100 | TonyStone | (~TonyStone@user/TonyStone) TonyStone |