[00:10:48] [02miraheze/ManageWiki] 07Universal-Omega pushed 031 commit to 03Universal-Omega-patch-1 [+0/-0/±1] 13https://git.io/JtacH [00:10:50] [02miraheze/ManageWiki] 07Universal-Omega 036b02f0a - fix [00:10:51] [02ManageWiki] 07Universal-Omega created branch 03Universal-Omega-patch-1 - 13https://git.io/vpSns [00:10:53] [02ManageWiki] 07Universal-Omega opened pull request 03#242: fix - 13https://git.io/Jtac7 [00:11:31] [02miraheze/ManageWiki] 07Universal-Omega pushed 031 commit to 03Universal-Omega-patch-1 [+0/-0/±1] 13https://git.io/Jtacd [00:11:33] [02miraheze/ManageWiki] 07Universal-Omega 0356e7101 - fix [00:11:34] [02ManageWiki] 07Universal-Omega synchronize pull request 03#242: fix - 13https://git.io/Jtac7 [00:11:59] miraheze/ManageWiki - Universal-Omega the build passed. [00:12:34] miraheze/ManageWiki - Universal-Omega the build passed. [00:14:53] !log reimage dbbackup1 (downgrade from 4GB MKVM to 2GB MKVM) [00:14:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:17:50] [02miraheze/puppet] 07Southparkfan pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtaCL [00:17:51] [02miraheze/puppet] 07Southparkfan 03c2af527 - dbbackup1: remove replication role [00:19:20] PROBLEM - graylog2 Current Load on graylog2 is CRITICAL: CRITICAL - load average: 4.38, 3.43, 2.29 [00:23:14] [02ManageWiki] 07Universal-Omega closed pull request 03#242: fix - 13https://git.io/Jtac7 [00:23:15] [02miraheze/ManageWiki] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/JtaCB [00:23:17] [02miraheze/ManageWiki] 07Universal-Omega 0378c4142 - fix (#242) * fix * fix [00:23:18] [02ManageWiki] 07Universal-Omega deleted branch 03Universal-Omega-patch-1 - 13https://git.io/vpSns [00:23:20] [02miraheze/ManageWiki] 07Universal-Omega deleted branch 03Universal-Omega-patch-1 [00:24:16] miraheze/ManageWiki - Universal-Omega the build passed. [00:26:04] [02miraheze/mediawiki] 07Universal-Omega pushed 031 commit to 03Universal-Omega-patch-6 [+0/-0/±1] 13https://git.io/JtaCi [00:26:05] [02miraheze/mediawiki] 07Universal-Omega 035cddfb4 - Update ManageWiki [00:26:07] [02mediawiki] 07Universal-Omega created branch 03Universal-Omega-patch-6 - 13https://git.io/vbL5b [00:26:28] [02mediawiki] 07Universal-Omega opened pull request 03#1145: Update ManageWiki - 13https://git.io/JtaCP [00:27:38] [02mediawiki] 07Universal-Omega closed pull request 03#1145: Update ManageWiki - 13https://git.io/JtaCP [00:27:39] [02miraheze/mediawiki] 07Universal-Omega pushed 031 commit to 03REL1_35 [+0/-0/±1] 13https://git.io/JtaC1 [00:27:41] [02miraheze/mediawiki] 07Universal-Omega 03e048b95 - Update ManageWiki (#1145) [00:27:42] [02miraheze/mediawiki] 07Universal-Omega deleted branch 03Universal-Omega-patch-6 [00:27:44] [02mediawiki] 07Universal-Omega deleted branch 03Universal-Omega-patch-6 - 13https://git.io/vbL5b [00:34:36] RECOVERY - graylog2 Current Load on graylog2 is OK: OK - load average: 1.23, 3.34, 3.29 [00:47:32] [02miraheze/dns] 07Southparkfan pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtaWw [00:47:34] [02miraheze/dns] 07Southparkfan 03b4be190 - Change dbbackup1 IPv6 and add dbbackup2 [00:50:33] !log graylog: change stream rules for MediaWiki Error Logs (matches all servers starting with 'test' now) [00:50:36] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:52:21] !log the same for all streams relevant for MediaWiki Engineers [00:52:23] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [01:00:29] [02miraheze/ManageWiki] 07Universal-Omega pushed 031 commit to 03revert-242-Universal-Omega-patch-1 [+0/-0/±2] 13https://git.io/JtaWQ [01:00:31] [02miraheze/ManageWiki] 07Universal-Omega 0344bb278 - Revert "fix (#242)" This reverts commit 78c4142d05476d370e379a8cc3ec9599e4ac3a6e. [01:00:32] [02ManageWiki] 07Universal-Omega created branch 03revert-242-Universal-Omega-patch-1 - 13https://git.io/vpSns [01:00:34] [02ManageWiki] 07Universal-Omega opened pull request 03#243: Revert "fix" - 13https://git.io/JtaW7 [01:00:38] [02ManageWiki] 07Universal-Omega closed pull request 03#243: Revert "fix" - 13https://git.io/JtaW7 [01:00:39] [02miraheze/ManageWiki] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/JtaW5 [01:00:41] [02miraheze/ManageWiki] 07Universal-Omega 037415f96 - Revert "fix (#242)" (#243) This reverts commit 78c4142d05476d370e379a8cc3ec9599e4ac3a6e. [01:00:42] [02miraheze/ManageWiki] 07Universal-Omega deleted branch 03revert-242-Universal-Omega-patch-1 [01:00:44] [02ManageWiki] 07Universal-Omega deleted branch 03revert-242-Universal-Omega-patch-1 - 13https://git.io/vpSns [01:01:11] !log purchased dbbackup2 [01:01:14] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [01:01:37] miraheze/ManageWiki - Universal-Omega the build passed. [01:01:39] miraheze/ManageWiki - Universal-Omega the build passed. [01:25:34] RECOVERY - bacula2 Bacula Databases db11 on bacula2 is OK: OK: Full, 541500 files, 40.45GB, 2021-02-07 01:25:00 (33.0 seconds ago) [01:55:42] [02miraheze/ManageWiki] 07Universal-Omega pushed 031 commit to 03revert-243-revert-242-Universal-Omega-patch-1 [+0/-0/±2] 13https://git.io/Jta4L [01:55:44] [02miraheze/ManageWiki] 07Universal-Omega 03e1025d1 - Revert "Revert "fix (#242)" (#243)" This reverts commit 7415f964436bf30ab5948e706f12a76bcd5eb8b7. [01:55:45] [02ManageWiki] 07Universal-Omega created branch 03revert-243-revert-242-Universal-Omega-patch-1 - 13https://git.io/vpSns [01:55:57] [02ManageWiki] 07Universal-Omega opened pull request 03#244: Revert "Revert "fix"" - 13https://git.io/Jta4t [01:56:02] [02ManageWiki] 07Universal-Omega closed pull request 03#244: Revert "Revert "fix"" - 13https://git.io/Jta4t [01:56:03] [02miraheze/ManageWiki] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/Jta4q [01:56:05] [02miraheze/ManageWiki] 07Universal-Omega 03b5f91ea - Revert "Revert "fix (#242)" (#243)" (#244) This reverts commit 7415f964436bf30ab5948e706f12a76bcd5eb8b7. [01:56:06] [02ManageWiki] 07Universal-Omega deleted branch 03revert-243-revert-242-Universal-Omega-patch-1 - 13https://git.io/vpSns [01:56:08] [02miraheze/ManageWiki] 07Universal-Omega deleted branch 03revert-243-revert-242-Universal-Omega-patch-1 [01:57:00] miraheze/ManageWiki - Universal-Omega the build passed. [01:57:07] miraheze/ManageWiki - Universal-Omega the build passed. [02:08:14] [02miraheze/ManageWiki] 07Universal-Omega pushed 031 commit to 03Universal-Omega-patch-1 [+0/-0/±1] 13https://git.io/Jta48 [02:08:16] [02miraheze/ManageWiki] 07Universal-Omega 0313a5b66 - update content model on the content table [02:08:17] [02ManageWiki] 07Universal-Omega created branch 03Universal-Omega-patch-1 - 13https://git.io/vpSns [02:08:19] [02ManageWiki] 07Universal-Omega opened pull request 03#245: update content model on the content table - 13https://git.io/Jta44 [02:09:21] miraheze/ManageWiki - Universal-Omega the build passed. [02:37:01] [02miraheze/puppet] 07Southparkfan pushed 031 commit to 03master [+2/-1/±2] 13https://git.io/JtaBc [02:37:02] [02miraheze/puppet] 07Southparkfan 03ad26d58 - Refactor database backup role, add dbbackup2 [02:39:37] PROBLEM - dbbackup2 Puppet on dbbackup2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [02:39:45] RECOVERY - bacula2 Bacula Databases db12 on bacula2 is OK: OK: Full, 304278 files, 45.75GB, 2021-02-07 02:38:00 (1.8 minutes ago) [02:39:56] PROBLEM - dbbackup1 Puppet on dbbackup1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [02:47:16] [02miraheze/puppet] 07Southparkfan pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtaBd [02:47:18] [02miraheze/puppet] 07Southparkfan 03620505d - dbbackup: fix data type [02:47:56] RECOVERY - dbbackup1 Puppet on dbbackup1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:50:09] [02miraheze/puppet] 07Southparkfan pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtaBN [02:50:11] [02miraheze/puppet] 07Southparkfan 035f9fcd7 - Run apt-get update when apt pins the mariadb package [02:51:10] PROBLEM - dbbackup1 MariaDB on dbbackup1 is CRITICAL: Host 'mon2.miraheze.org' is not allowed to connect to this MariaDB server [02:51:11] PROBLEM - dbbackup2 Check MariaDB Replication on dbbackup2 is UNKNOWN: NRPE: Unable to read output [02:51:20] PROBLEM - dbbackup1 Check MariaDB Replication on dbbackup1 is UNKNOWN: NRPE: Unable to read output [02:51:53] PROBLEM - dbbackup2 MariaDB on dbbackup2 is CRITICAL: Can't connect to MySQL server on 'dbbackup2.miraheze.org' (111) [02:53:27] RECOVERY - dbbackup2 Puppet on dbbackup2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:17:38] !log start mariabackup on db11 and db12 [03:17:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:25:45] PROBLEM - ping6 on dbbackup2 is WARNING: PING WARNING - Packet loss = 0%, RTA = 102.69 ms [03:45:48] PROBLEM - db11 Current Load on db11 is CRITICAL: CRITICAL - load average: 8.74, 7.36, 6.11 [03:49:47] PROBLEM - db11 Current Load on db11 is WARNING: WARNING - load average: 7.60, 7.67, 6.53 [03:59:43] RECOVERY - db11 Current Load on db11 is OK: OK - load average: 6.08, 6.59, 6.61 [04:02:06] [02puppet] 07Universal-Omega opened pull request 03#1637: Update PHP comment to cloud 4 and 5 not 1 and 2 - 13https://git.io/JtaEb [04:21:59] RECOVERY - bacula2 Bacula Databases db13 on bacula2 is OK: OK: Full, 207255 files, 80.26GB, 2021-02-07 04:21:00 (58.0 seconds ago) [04:33:15] [02puppet] 07Universal-Omega opened pull request 03#1638: Remove old - 13https://git.io/JtauB [04:35:09] [02puppet] 07Universal-Omega edited pull request 03#1638: Remove old - 13https://git.io/JtauB [06:11:43] [02puppet] 07Reception123 closed pull request 03#1637: Update PHP comment to cloud 4 and 5 not 1 and 2 - 13https://git.io/JtaEb [06:11:44] [02miraheze/puppet] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jtazj [06:11:46] [02miraheze/puppet] 07Universal-Omega 032dba55c - Update PHP comment to cloud 4 and 5 not 1 and 2 (#1637) [06:59:56] PROBLEM - ping6 on dbbackup2 is CRITICAL: PING CRITICAL - Packet loss = 100% [07:01:58] PROBLEM - ping6 on dbbackup2 is WARNING: PING WARNING - Packet loss = 0%, RTA = 101.48 ms [08:13:44] PROBLEM - ping4 on ns1 is WARNING: PING WARNING - Packet loss = 0%, RTA = 126.35 ms [08:17:42] RECOVERY - ping4 on ns1 is OK: PING OK - Packet loss = 0%, RTA = 99.39 ms [09:39:06] Hello egoish[m]! If you have any questions, feel free to ask and someone should answer soon. [10:04:35] PROBLEM - cloud4 Current Load on cloud4 is WARNING: WARNING - load average: 20.86, 18.29, 16.27 [10:06:33] RECOVERY - cloud4 Current Load on cloud4 is OK: OK - load average: 15.78, 17.57, 16.27 [11:25:25] PROBLEM - gluster3 Current Load on gluster3 is WARNING: WARNING - load average: 5.12, 4.41, 3.60 [11:27:24] RECOVERY - gluster3 Current Load on gluster3 is OK: OK - load average: 2.64, 3.79, 3.48 [15:19:53] PROBLEM - ping6 on dbbackup2 is CRITICAL: PING CRITICAL - Packet loss = 60%, RTA = 101.82 ms [15:21:55] PROBLEM - ping6 on dbbackup2 is WARNING: PING WARNING - Packet loss = 0%, RTA = 102.23 ms [15:28:08] fyi for all, #miraheze-sre is now the public channel for technical discussions related to Miraheze, and where the bots will be moving to at some point in the next 24 hours. Naturally this channel remains the community and help-based channel - just hopefully now with less noise in between discussions and help requests :) [15:30:05] PROBLEM - gluster3 Current Load on gluster3 is WARNING: WARNING - load average: 5.54, 4.47, 3.89 [15:32:01] RECOVERY - gluster3 Current Load on gluster3 is OK: OK - load average: 4.24, 4.65, 4.04 [15:35:28] PROBLEM - cloud4 Current Load on cloud4 is WARNING: WARNING - load average: 21.68, 20.22, 17.51 [15:35:50] PROBLEM - gluster3 Current Load on gluster3 is CRITICAL: CRITICAL - load average: 9.02, 6.79, 5.02 [15:37:24] RECOVERY - cloud4 Current Load on cloud4 is OK: OK - load average: 16.84, 19.30, 17.52 [15:37:45] PROBLEM - gluster3 Current Load on gluster3 is WARNING: WARNING - load average: 4.87, 5.83, 4.87 [15:41:02] Cool! [15:41:35] RECOVERY - gluster3 Current Load on gluster3 is OK: OK - load average: 4.06, 4.83, 4.68 [15:52:04] [02miraheze/puppet] 07Southparkfan pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtaF5 [15:52:05] [02miraheze/puppet] 07Southparkfan 035931301 - Fix firewall rules for connections from db backup servers [15:54:02] !log started replication flow from db12 -> dbbackup2 [15:54:05] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [15:58:13] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/Jtabq [15:58:15] [02miraheze/puppet] 07paladox 0380fde3b - Switch from #miraheze to #miraheze-sre for the bots [15:58:16] [02puppet] 07paladox created branch 03paladox-patch-1 - 13https://git.io/vbiAS [15:58:17] !log started replication flow from db11 -> dbbackup1 [15:58:18] [02puppet] 07paladox opened pull request 03#1639: Switch from #miraheze to #miraheze-sre for the bots - 13https://git.io/Jtabm [15:58:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [15:59:02] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JtabG [15:59:04] [02miraheze/puppet] 07paladox 03bc66841 - Update config.py [15:59:05] [02puppet] 07paladox synchronize pull request 03#1639: Switch from #miraheze to #miraheze-sre for the bots - 13https://git.io/Jtabm [16:00:04] [02puppet] 07paladox closed pull request 03#1639: Switch from #miraheze to #miraheze-sre for the bots - 13https://git.io/Jtabm [16:00:05] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/Jtab8 [16:00:07] [02miraheze/puppet] 07paladox 03eb7a219 - Switch from #miraheze to #miraheze-sre for the bots (#1639) * Switch from #miraheze to #miraheze-sre for the bots * Update config.py [16:00:08] [02puppet] 07paladox deleted branch 03paladox-patch-1 - 13https://git.io/vbiAS [16:00:10] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-1 [16:21:46] .op [16:21:46] Attempting to OP... [16:23:30] Please note: Due to an ongoing incident, InstantCommons / Anything else loaded from wikimedia sites may be slow or fail, especially for users in Europe. This is an upstream issue and we have no further information. [16:35:00] Note: The above should be fixed. If it's still an issue please alert us. [16:36:59] [02miraheze/ManageWiki] 07Universal-Omega pushed 031 commit to 03Universal-Omega-patch-1 [+0/-0/±1] 13https://git.io/JtaA5 [16:37:01] [02miraheze/ManageWiki] 07Universal-Omega 0366d4aef - Fix moving back to original namespace afterwards [16:37:02] [02ManageWiki] 07Universal-Omega synchronize pull request 03#245: update content model on the content table - 13https://git.io/Jta44 [16:37:31] [02ManageWiki] 07Universal-Omega edited pull request 03#245: update content model on the content table; fix moving page back to original namespace - 13https://git.io/Jta44 [16:38:12] miraheze/ManageWiki - Universal-Omega the build passed. [16:45:05] this page does not exist but https://revi.wiki/w/index.php?title=%ED%8B%80:Revi.kr_list&curid=304&diff=3473&oldid=3472 does exist, where is my cat? https://usercontent.irccloud-cdn.com/file/YETYDY6L/image.png [16:45:06] [ "Template:Revi.kr list"의 두 판 사이의 차이 - ReviNet ] - revi.wiki [16:45:32] schrodinger forgot to bring my cat. [16:46:05] revi: is it translated namespace name at fault? [16:46:24] Uhm.... the interface language is Korean [16:46:38] wiki interface lang* [16:46:56] and my local language is set to English, so it is correct to have the NS name in Korean [16:47:13] revi: yeah but for some reason it's not impacting namespace names [16:47:20] It's inconsistent [16:47:43] I don't get it, I never observed this behavior until today. [16:48:41] If this is an issue related to localisation: I have noticed this issue on Meta while translating pages today. [16:49:18] I can affirm there was no such behavior before 06:00 UTC today [16:49:57] Something is weird with localisation but I don't have an answer yet [16:50:05] Though that was a little different and the issue was that the relevant i18n key was shown instead of the string. [16:50:10] It's inconsistent and doesn't make sense [16:50:17] That one I saw it as well. [16:50:26] @R4356th: which key? [16:50:28] so there was nothing problematic before today, and it all emerged today. [16:50:29] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_35 [+0/-0/±1] 13https://git.io/Jtaxr [16:50:30] [02miraheze/mediawiki] 07paladox 036903fb6 - Update Translate [16:50:41] Keys provided by the Translate extension. [16:50:45] Thanks, paladox. [16:50:46] revi: first report was when the infra moved over [16:51:03] maybe, but translate extension is disabled on reviwikiwiki [16:51:20] can't repro the same issue on WMF [16:52:39] revi: it's core MediaWiki is namespace name so it'll be core somehwere I'd guess [16:52:49] but you only run on Stable [16:52:53] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_35 [+0/-0/±1] 13https://git.io/JtaxD [16:52:54] [02miraheze/mediawiki] 07paladox 03f8801ea - Update UniversalLanguageSelector [16:53:00] @R4356th: given it only happened when we changed infra, I'd doubt it would be [16:53:20] then why didn't this happen during all the previous times with 1.35.1? [16:53:23] doesn't also make sens [16:53:26] sense* [16:54:01] last time I edited ManageWiki was 27 January 2021 so I didn't touch anything for last few days [16:54:08] Because something has gone wrong I'd guess with not changing something over with the new infra [16:54:22] It's the only change since when it started that could effect it [16:55:38] At least I can leave with these as long as you fix the page load slowness issues. [16:55:49] It is taking minutes for pages to finish loading. [16:56:06] yeah, definitely something gone rogue https://usercontent.irccloud-cdn.com/file/nISDJRd6/image.png [16:56:22] purge doesn't help [16:58:02] * RhinosF1|NotHere knows [16:58:38] issue seems to happen on mw 10/11 [16:58:41] but not on mw8/9 [16:58:52] There is https://github.com/miraheze/puppet/blob/111e92317ba362018ff75b90d3dd2354c15f4f4b/modules/mediawiki/manifests/cron.pp#L7 [16:58:53] [ puppet/cron.pp at 111e92317ba362018ff75b90d3dd2354c15f4f4b · miraheze/puppet · GitHub ] - github.com [16:59:04] paladox: is that cron installed everywhere? [16:59:08] Like actually check [16:59:54] yes [16:59:55] 0 23 * * * /usr/bin/nice -n 15 /usr/bin/php /srv/mediawiki/w/extensions/LocalisationUpdate/update.php --wiki loginwiki > /var/log/mediawiki/debuglogs/l10nupdate.log [17:01:40] paladox: I'm confused. What's different between the two servers? [17:01:47] i'm not sure [17:01:52] there should be no difference [17:01:55] Apart from the hostname being 2 digits and not 1 [17:02:08] But could that really cause something to change [17:02:26] Puppet site.pp accounts fine for it [17:03:49] paladox: I have a theory [17:04:00] Does [0-9] only match single digits [17:04:00] ? [17:04:08] i think so [17:04:37] That might be it [17:04:49] As a few configs use mw[0-9] [17:05:02] what might? Where is the problem or where is the regex? [17:07:09] Hello Mamilo! If you have any questions, feel free to ask and someone should answer soon. [17:07:10] 你好,我讨厌所有人,一切都笑了,这是我不知道的米拉米拉东西,但这很奇怪 [17:07:11] 你好,我讨厌所有人,一切都笑了,这是我不知道的米拉米拉东西,但这很奇怪 [17:07:12] 你好,我讨厌所有人,一切都笑了,这是我不知道的米拉米拉东西,但这很奇怪 [17:07:13] 你好,我讨厌所有人,一切都笑了,这是我不知道的米拉米拉东西,但这很奇怪 [17:07:34] paladox: I'm not sure the case I've found is the cause but we probably need to look deeper [17:07:45] you need to explain [17:07:50] because i don't understand. [17:08:04] where is the code that you think is problomatic? [17:10:15] Hello Mandol! If you have any questions, feel free to ask and someone should answer soon. [17:10:16] Do you speak mandarin [17:10:18] 只要听我说, 说实话, 你米拉米拉人来听我出来已经很烦人, 你不明白米拉米拉 [17:10:18] 只要听我说, 说实话, 你米拉米拉人来听我出来已经很烦人, 你不明白米拉米拉 [17:10:19] 只要听我说, 说实话, 你米拉米拉人来听我出来已经很烦人, 你不明白米拉米拉 [17:10:19] 只要听我说, 说实话, 你米拉米拉人来听我出来已经很烦人, 你不明白米拉米拉 [17:11:03] hmm [17:12:36] paladox: I saw a commit on github's search but it wasn't looking at master [17:12:49] link [17:13:24] There was https://github.com/miraheze/mw-config/commit/a7ef94838bb5ff77ea65400dfd098a7d7566d13d [17:13:25] [ Add test[0-9] to regex · miraheze/mw-config@a7ef948 · GitHub ] - github.com [17:13:33] But I'm either really blind or that code has been moved [17:14:10] thats been removed [17:14:16] we only needed it fro test3 [17:14:59] Okay [17:15:30] jess: proxy for why the bot banned [17:15:54] paladox: is there anything else matching on mw[0-9] can you grep puppet/mw-config [17:15:58] Hello Yoninino! If you have any questions, feel free to ask and someone should answer soon. [17:16:03] dmehus JohnLewis paladox Reception123 RhinosF1|NotHere SPF|Cloud Univresal_Omega Zppix SPEAK MANDARIN SPEAK MANDARIN SPEAK MANDARIN SPEAK MANDARIN [17:16:14] i think i might want to involve myself in this [17:16:33] !log depool mw10, reboot and repool [17:17:06] .op [17:17:06] Attempting to OP... [17:17:08] https://revi.wiki/wiki/%ED%8B%80:Revi.kr_list works on mw10 now [17:17:10] [ 틀:Revi.kr list - ReviNet ] - revi.wiki [17:17:22] niase [17:17:24] naise* [17:18:05] *!*@37.46.115.10/24 would be better [17:18:14] does the same thing but Betterer [17:18:20] oh, thanks, didn't realize CIDR ranges worked on IRC [17:18:23] !log depool mw11, reboot and repool [17:18:26] thought IRC uses wildcards [17:18:34] paladox: rebooting servers every day is not a solution [17:18:42] How do I modify an existing block, or do I have to unblock and reblock? [17:18:46] indeed [17:18:50] add new and remove [17:18:53] but i don't know what the issue is [17:18:58] ah, thanks, @Majavah [17:19:02] I didn't know either, I thought you could only do .* [17:19:21] CIDR support is also news for me :D [17:19:25] irc usually uses wildcards but freenode supports cidr notation [17:19:30] which, in my opinion, is fucking awesome [17:19:38] /22 comes in handy [17:20:11] Hrm, didn't work for me when I issued `*!*@37.46.115.10/24` [17:20:16] oops [17:20:18] there's a reason cidr was created after class [abc] networks were used [17:20:22] `/ban *!*@37.46.115.10/24` [17:20:29] maybe have to unblock first [17:20:43] try setting the mode directly? [17:20:59] yeah you can't set bans that cover the same thing as other bans [17:21:04] nor subsets, only supersets [17:21:05] which is stupid [17:21:07] ah [17:21:18] there we go :) [17:21:25] .op [17:21:31] is it an op party [17:21:35] lol [17:21:46] .deop [17:23:09] but yeah, jess, CIDR notation would be handy for /22 and /23 blocks [17:30:21] Hello MacGuffin! If you have any questions, feel free to ask and someone should answer soon. [17:30:50] Hi:)  I have a MediaWiki question: how can I make the title of a page to start with a lower case letter? [17:30:50] Hi [17:31:06] MacGuffin: it should be in Special:ManageWiki/settings [17:31:38] @MacGuffin, yeah, I think the variable you want is `$wgCapitalLinks` iirc [17:32:16] Under links [17:32:20] Oh, I want it to be only for a specific page [17:32:23] not in general [17:32:25] oh [17:32:31] I note that in Wikipedia they ar using [17:32:33] `{{DISPLAYTITLE:pagename}}` [17:32:47] Put ^ on the page [17:32:48] `{{lowercase}}` [17:32:50] but you'll need to unrestrict displaytitle in ManageWiki/settings [17:32:57] aIn the top of the page, but it didn't work [17:33:02] It won't change the link but it'll change how it looks [17:33:13] {{lowercase}} is custom made template [17:33:20] @MacGuffin, did you change the ManageWiki/settings to unrestrict displaytitle? [17:33:24] DISPLAYTITLE is global [17:33:30] Oh I see, thanks! [17:33:31] Part of MediaWiki [17:33:32] you have to do that wiki wide or it won't work [17:33:33] Let me check that [17:33:40] @MacGuffin, np [17:34:33] dmehus: can we get watchlist expiry on meta? [17:34:47] Is it in MW 1.35? [17:34:57] Yeah but it's behind ManageWiki [17:35:00] It's a setting [17:35:04] but if so, I see no problem with that as it's just a technical change [17:35:11] Okay, I'll do that now then [17:35:22] It works, thanks! [17:35:34] No problem [17:36:53] dmehus: when did IRC become Discord [17:37:00] You did that on loginwiki [17:37:00] lol [17:37:03] I did it again [17:37:06] I always do that [17:37:20] should do I revert and redo my log summary? [17:37:53] .tell MacGuffin that's great :) [17:37:53] dmehus: I'll pass that on when MacGuffin is around. [17:38:34] dmehus: no you're fine, it does relay [17:38:45] RhinosF1, oh true, good point :P [17:39:10] I did see it on Discord afterall...just not before I saw it on IRC :P [17:39:25] Ye [17:46:40] TIL: Can do CIDR bans [17:46:53] (@Freenode) [18:30:45] revi, heh that's cool you learned that, too :) [18:31:02] yeah, I usually just let my friendly `wmopbot` handles it tho [18:31:12] `!kb (you)` and ppooooff done [18:37:06] oh, heh, cool [18:47:18] it's helpful when there's someone evading in subnets, like that person was [18:47:25] it's especially helpful for a network operator [19:15:22] jess, ah [19:15:39] .op [19:16:32] .deop [19:17:24] Have the bots veebmoved? [19:19:41] As it seems they have been, what I am very glad of as they was very annoying and spammy [19:19:51] Yep [19:20:01] Now #miraheze-sre [19:20:03] THank the Lord and Lady [19:21:08] RhinosF1|NotHere, I just hate it when bots spam a channel [19:21:20] They don't spam per se [19:21:51] Well, I knew someone that had a bot with a "yay" command and people aways spammmed it [19:22:14] I hate that bot. I don't hate the Miraheze bots that much as I lknow they are usful [19:24:34] MirahezeBot is rate limited to avoid that on some commands [19:27:26] That is good [19:27:46] .tell MirahezeBot you are a nice bot [19:27:46] BurningPrincess1: I'm here now; you can tell me whatever you want! [19:28:22] BurningPrincess1: Thank you! I appreciate your nice comments :) [19:28:46] (the latter message was me :P) [19:28:56] :) [19:29:46] I like bots that do usful things, (tell is a handy command) on Discord I like anti raid bots,but dislike game bots [19:30:26] MirahezeBot has an anti spam tool built in [19:30:35] How handy [19:31:02] It mostly triggers on open proxies [19:31:11] It does annoy me when ppl spam IRC channels [19:32:02] I noticed the Chinese spammer guy a few hours ago [19:33:28] ni hao [19:33:33] [02miraheze/mw-config] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/JtVT4 [19:33:34] [02miraheze/mw-config] 07paladox 03d1b87c4 - Use #miraheze-sre for notifications [19:33:36] [02mw-config] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vbvb3 [19:33:38] [02mw-config] 07paladox opened pull request 03#3719: Use #miraheze-sre for notifications - 13https://git.io/JtVTB [19:33:40] [02mw-config] 07paladox edited pull request 03#3719: ci: Use #miraheze-sre for notifications - 13https://git.io/JtVTB [19:33:44] whoa [19:34:15] [02mw-config] 07paladox closed pull request 03#3719: ci: Use #miraheze-sre for notifications - 13https://git.io/JtVTB [19:34:17] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtVTE [19:34:18] [02miraheze/mw-config] 07paladox 0333622e9 - Use #miraheze-sre for notifications (#3719) [19:34:20] [02mw-config] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vbvb3 [19:34:21] [02miraheze/mw-config] 07paladox deleted branch 03paladox-patch-2 [19:34:32] Someone kick that bot please [19:35:08] Anyone know any good examples of wikibase being used on miraheze? [19:38:50] BurningPrincess1: NDKilla [19:39:05] egoish[m]: there's @Avengium's wiki [19:39:10] But I can't spell it [19:40:11] Thank you. I'll try to find it [19:41:01] What? [19:41:06] egoish[m]: yourcreatures is one [19:41:14] But the other 2 linked are Spanish [19:41:46] I'm ok with Spanish. Crammed a bunch of duolingo time in during quarantine. Thanks [19:52:23] Hi Voidwalker, Steward of Miraheze [19:53:31] hi [20:06:51] * hispano76 greets [20:16:28] hi @Hispano76 🙂 [20:20:53] Do you think I requets too ,many wikis [20:24:13] Zppix: around? [20:31:19] [02miraheze/phabricator-extensions] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtVLt [20:31:20] [02miraheze/phabricator-extensions] 07Universal-Omega 030a1b0a8 - Use #miraheze-sre (#10) [20:49:46] Tonight, we say goodbye to icinga-miraheze, who has moved on to another channel and has left #miraheze forever. I'm sure many will rejoice at this departure :P [20:53:24] heh, I might even remove it from my ignore list :P [20:55:00] heh [20:55:07] and soon Not-* will be leaving us too [20:55:33] It has [20:58:41] ah [20:58:52] well then this channel is now Tech-related bot free [20:58:56] and will be much more silent [21:00:17] .kick Not-7024 [21:00:18] Please wait... [21:10:33] Doi I ask fro too many wikis? [21:29:50] Voidwalker, lol I didn't know you'd been ignoring icinga-miraheze and/or Not-* [21:30:07] @Naleksuh will be happy as well :) [21:30:27] You found out the proper way to use IRC [21:30:33] heh yes [21:30:39] no more firehose in the office :P [21:30:41] dmehus, poke :) [21:30:55] @BurningPrincess1, getting there, will look in a bit [21:32:54] I dislike the "firehose in the office" analogy, monitoring is a vitally important tool. To down talk the importance of such monitoring would be to standardise the fact that downtime is acceptable and problems being undetected is preferred over being aware of how the infrastructure is performing [21:33:48] Oh, I don't think it downplays the importance of monitoring though, so think the analogy is okay. [21:34:28] It's used in such a way to complain about the monitoring though [21:34:29] How many custom namespaes could a wiki have total? [21:34:41] We've just moved firehouse out of the board room and into the I.T. monitoring room [21:34:58] JohnLewis, oh okay, fair enough, I guess heh [21:35:15] s/firehouse/firehose [21:35:15] dmehus meant to say: We've just moved firehose out of the board room and into the I.T. monitoring room [21:35:43] I prefer monitering bots to be in their own channels, not the support channel [21:35:47] BurningPrincess1 as many as you want [21:35:55] This originally existed the sole channel for Miraheze and the de-facto technical channel, so it was much rather the correct and preferred place to have it [21:35:58] there's no arbitrary limit. [21:36:02] @BurningPrincess1 No limit, as far as I'm aware, unless there's a 4-5 digit limit on namespace IDs, then I guess 10,000 or 100,000 [21:36:50] dmehus, I like the idea of hnaving a namspcae for each major world (or sinlar depending on what your wiki for ) as it means being ale to filter them in AllPages [21:37:03] JohnLewis, yeah, that's true, and that was also this channel was used for more than just reporting technical issues [21:37:28] @BurningPrincess1 Yeah, that's one advantage for sure, though categories are another way to achieve that as well [21:37:40] s/also this/also before this [21:37:41] dmehus meant to say: JohnLewis, yeah, that's true, and that was also before this channel was used for more than just reporting technical issues [21:38:00] dmehus, I use both, I tend to have redundant methiods iun stuff [21:38:07] I'm aware, my point is just that until today, this was the correct place for the monitoring alerts, as until today, it still remained the sole technical channel for Miraheze [21:40:27] True, and I'm just saying that I don't personally believe that analogy downplayed the importance of monitoring alerts. If anything, it was a written commentary on the sub-optimal organization of technical discussions and system reports / problems / monitoring, so I guess there's multiple lens through which that analogy can be viewed [21:41:11] The analogy normalised the complaining over monitoring - that's a black and white breakdown of it :) [21:41:29] It's not my analogy, though [21:41:34] I know [21:41:46] Oh yeah misread, you didn't say it was [21:41:48] my bad [21:41:49] heh [21:41:58] but yeah that's true [21:46:22] What are the specs of the database servers storing the AllTheTropes wiki? [21:48:07] 1.9 NVME 4 (cores) [21:48:17] *1.9tb [21:51:51] Re Namespaces, I think it's 999 custom ones but it depends on manage wiki. All the current ones are 4 digits so in theory up to 9999 would work. [21:51:58] BurningPrincess1: ^ [21:52:06] Thank you, RhinosF1|NotHere [21:52:14] More like RhinosF1|here [21:52:43] RhinosF1|NotHere, I think say 999,000 pages would be a lot (assuming 1000 per namespace) [21:54:16] JohnLewis: is all manage wiki custom ones 3xxx? [21:54:21] Or Universal_Omega ^ [21:54:29] 3000+ [21:54:53] JohnLewis: cool, can you go over 4 digits? [21:55:09] nope [21:55:21] ah, good to know [21:55:45] So it's 7000 namespaces then custom [21:55:50] so 7,000ish namespaces, which should be sufficient. I wouldn't want to manage a wiki with that many namespaces anyway [21:55:50] Fun fact [21:56:20] I doght I will come up with 6999 worldbuilding projects [21:56:29] well, 3500 namespaces [21:56:51] Oh ye talk as well [21:57:01] 3500 normal + 3500 talk [21:57:13] * RhinosF1|NotHere wonders what the highest a wiki has is [21:57:28] I don't think i could even come up with 3500 worldbuilding projects [21:58:45] I mean, I have about 4 ideas/or minorly built ones [21:59:06] https://www.irccloud.com/pastebin/gQ2s4uRd/ [21:59:06] [ Snippet | IRCCloud ] - www.irccloud.com [22:01:09] JohnLewis: that'll be 1252 custom ones then? [22:01:18] RhinosF1: 3000-4999 are the namespaces reserved for custom namespaces, going over that could cause extension conflicts and issues, the highest index possible from any extension, etc... is a little over 32000 to my knowledge. [22:01:42] Universal_Omega: cool [22:09:53] @Universal_Omega ah, yeah that makes sense then [22:11:09] and @JohnLewis, good point. My math was off (as usual) with the talk namespaces representing half of that number [22:38:31] heyo [22:38:32] Xana: 2021-01-31 - 07:31:04UTC tell Xana You can try asking your question in #mediawiki-visualeditor. [22:38:44] ah thanka [22:38:51] tho now i have a new question [22:39:17] Ask away [22:39:34] I wanna change the name and purpose of the wiki i have. Would it be easier to make a new wiki or just make mine private? [22:39:52] Do i have to remove prior cookies to make a wiki private from being public? [22:40:06] You don't to the cookie question [22:40:15] sweet sweet [22:40:31] Welp, i'll just make my wiki private [22:40:37] thanks for the info [22:40:46] Changing the name and purpose, if you want the subdomain changing then request a new one [22:41:56] dmehus: don't forget with .tell over discord you need to sign your message with a name or say who you are somewhere [22:54:51] @RhinosF1|NotHere Oh, did I leave a tell from Discord? I think @R4356th might've left that tell actually, as I left Xana a tell from IRC and it was a bit different [22:55:27] dmehus: then same message to @R4456th and apologies for assuming it was you [22:56:12] RhinosF1|NotHere, no problem. It does sound like something I'd say. Can you use `s/R4456th/R4356th`? [22:56:42] s/R44/R43 [22:56:42] RhinosF1|NotHere meant to say: dmehus: then same message to @R4356th and apologies for assuming it was you [22:56:47] ty [22:58:11] See you probably Wednesday, I'm off to sleep [23:06:02] Command sent from Discord by Doug: [23:06:02] .tell RhinosF1 okay, night. sleep well. Sent by @Doug [23:06:03] MH-Discord: I'll pass that on when RhinosF1 is around. [23:07:00] Command sent from Discord by Doug: [23:07:01] .tell dmehus @Doug test [23:07:01] MH-Discord: I'll pass that on when dmehus is around. [23:07:22] test [23:07:22] dmehus: 2021-02-07 - 23:07:01UTC tell dmehus @Doug test [23:08:00] Aww, it's too bad MirahezeBot couldn't parse the first word of a tell as the sender of the tell instead of MH-Discord [23:10:53] * dmehus wonders how many IRC users have accidentally created a conversation with "ChanServe" instead of "ChanServ" due to an obvious typo