[00:06:17] [1/3] Just a heads up for MH, since the GitHub repo keeps in sync with mediawiki core, that it's likely the GitHub mirror of MediaWiki core will most likely stop existing after the switch to GitLab: [00:06:17] [2/3] > The canonical repo is planned to move from Gerrit to GitLab, yes. The GitHub mirror will likely stop existing [00:06:18] [3/3] (https://discord.com/channels/178359708581625856/935223464229470259/1172324011280183326) [00:14:19] wait. github which has been the go-to forever, even for us non-techis, is gonna disappear, replaced by gitlab? [00:19:49] oh they moving? [00:22:03] github isn't dissapearing as in alltogether, just that the Foundation mirrors gerrit config to github, but they are moving from gerrit to GitLab so apparently it is likely the github mirror will dissapear, or so taavi says [00:22:11] yeah, been in motion for YEARS [00:22:29] GitLab > GitHub imo anyway [00:24:59] Any way for us to set up a GitLab Github mirror? [00:26:03] Yeah you can [00:26:20] Just going off what taavi said, it may very well stay. [17:32:06] think the jobs slowness is our end @rhinosf1 [17:32:18] we're currently looking into why jobs are slow [17:32:24] think i found a hint [17:35:07] one of the commons ip is failing for us? [17:35:10] [1/5] > root@mwtask141:/srv/mediawiki/config# ping6 2a02:ec80:300:ed1a::1 [17:35:11] [2/5] > PING 2a02:ec80:300:ed1a::1(2a02:ec80:300:ed1a::1) 56 data bytes [17:35:11] [3/5] > ^C [17:35:11] [4/5] > --- 2a02:ec80:300:ed1a::1 ping statistics --- [17:35:12] [5/5] > 3 packets transmitted, 0 received, 100% packet loss, time 2037ms [17:39:02] users been reporting problems w/ Wikimedia Commons for almost a day now [17:39:49] Intresting [17:40:08] it works for me on my mac tho [17:44:22] @paladox can you ping / mtr it? [17:45:03] i've notified one of their netops [17:45:50] Which one [17:47:03] topranks [18:03:54] oh [18:06:36] @rhinosf1 they have resolved it for now although they are still looking [18:08:46] @orduin fyi ^ [18:09:56] @paladox want to retry then? [18:10:15] retry parsoid? Not at the moment. I'm running the queue at the moment. [18:10:18] also [18:10:29] we have a problem with the jobqueue metric thing [18:10:38] Okay [18:10:41] What's the issue [18:10:45] it was causing things to go slower and cause latency to go up [18:11:03] 17:48:28 !log withdrawing IPv6 prefixes announced to AS1299 in esams to troubleshoot connectivity problem report [18:12:33] How? [18:13:08] i don't know yet although i suspect could be because redis is single threaded. But also all the keys it was looking for. [18:13:12] also seems there's duplicates [18:13:27] we do * but then we also look at all the jobs listed as well. That's quite a waste [18:13:48] I wonder if it's the way we count