[00:01:43] RECOVERY - cp8 Disk Space on cp8 is OK: DISK OK - free space: / 4045 MB (20% inode=93%); [00:04:25] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 19.79, 23.04, 17.68 [00:08:33] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 13.05, 18.74, 17.22 [00:55:07] [02puppet] 07paladox synchronize pull request 03#1375: openldap: Create read only user - 13https://git.io/Jf4b1 [00:55:08] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-3 [+0/-0/±1] 13https://git.io/JfNfc [00:55:10] [02miraheze/puppet] 07paladox 033666992 - Update openldap.pp [00:55:22] [02puppet] 07paladox edited pull request 03#1375: openldap: redo access permissions - 13https://git.io/Jf4b1 [00:55:52] [02puppet] 07paladox edited pull request 03#1375: openldap: redo access permissions - 13https://git.io/Jf4b1 [01:15:47] Void, Reception either of you around? [01:20:26] QuIRC, yeah, what's up? [01:20:44] DM? [01:20:52] go ahead [01:43:05] !log reinstall ldap on ldap1 [01:43:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [01:43:17] [02puppet] 07paladox closed pull request 03#1375: openldap: redo access permissions - 13https://git.io/Jf4b1 [01:43:19] [02miraheze/puppet] 07paladox pushed 035 commits to 03master [+0/-0/±5] 13https://git.io/JfNJC [01:43:20] [02miraheze/puppet] 07paladox 036200782 - Merge pull request #1375 from miraheze/paladox-patch-3 openldap: redo access permissions [01:43:22] [02puppet] 07paladox deleted branch 03paladox-patch-3 - 13https://git.io/vbiAS [01:43:23] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-3 [01:44:34] [02mw-config] 07paladox closed pull request 03#3119: Remove wgJobQueueAggregator - unused - 13https://git.io/JfbMj [01:44:36] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNJW [01:44:37] [02miraheze/mw-config] 07paladox 0392dd4e1 - Remove wgJobQueueAggregator - unused (#3119) [01:44:41] [02mw-config] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vbvb3 [01:44:42] [02miraheze/mw-config] 07paladox deleted branch 03paladox-patch-2 [01:46:18] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNJB [01:46:19] [02miraheze/puppet] 07paladox 0382131ad - fix [02:39:56] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNU8 [02:39:58] [02miraheze/ssl] 07paladox 03f93980f - Remove aman.info.tm [02:42:38] RECOVERY - cp6 Puppet on cp6 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [02:43:06] RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [02:43:07] RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [02:43:31] RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [02:43:35] RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [02:43:59] RECOVERY - cp8 Puppet on cp8 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [02:44:10] RECOVERY - cp7 Puppet on cp7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:44:20] RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:46:52] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:35:13] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNTO [03:35:14] [02miraheze/services] 07MirahezeSSLBot 0303a5edf - BOT: Updating services config for wikis [04:42:46] hello friends! I am trying to get CommentStreams installed on solarawiki. I see I've got the new ManageWiki options, and the namespaces have been created, but I don't see the actual comment box on any page :( [04:46:05] is the update.php script ran immediately after adding an extension? or maybe there's a cron I'm waiting on? [04:51:59] musikanimal: suspect you need to restart the service after adding an extension [04:52:13] the PHP daemon, that is [04:54:29] you think? most extensions "just work". Most :) [04:55:00] except the ones we need :) [04:55:50] who would be able to restart it for me? [04:56:55] whomever has superuser access on the box? [04:57:00] i.e. not me [04:59:51] musikanimal: give it a few minutes maybe [04:59:59] sure [05:02:53] hd1: hello how can we help you? [05:03:57] Zppix: thanks for the offer, but I'm probably better suited to provide help rather than request it [05:04:10] hows that/ [05:04:58] hows that so? hd1 [05:11:53] https://spcodex.wiki/wiki/Special:AllComments works. It's just the comment form itself that's missing. Should by default be in the mainspace. [05:11:54] [ All Comments - SPCodex ] - spcodex.wiki [05:13:00] I tried using the `` tag to force it to show, no dice :( [05:15:14] im sorry musikanimal i would help furher but its 12:14AM here and i just got off work a couple hours ago after working 8 hours [05:15:31] no worries! get some rest [05:20:23] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNLG [05:20:25] [02miraheze/services] 07MirahezeSSLBot 0371e0636 - BOT: Updating services config for wikis [05:34:43] PROBLEM - wiki.edhel.online - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.edhel.online and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [05:36:43] RECOVERY - wiki.edhel.online - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.edhel.online' will expire on Fri 18 Sep 2020 06:26:09 GMT +0000. [06:25:35] PROBLEM - wiki.edhel.online - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.edhel.online and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [06:27:33] RECOVERY - wiki.edhel.online - LetsEncrypt on sslhost is OK: OK - Certificate 'edhel.online' will expire on Fri 18 Sep 2020 06:20:45 GMT +0000. [07:16:11] PROBLEM - wiki.edhel.online - LetsEncrypt on sslhost is CRITICAL: connect to address wiki.edhel.online and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [07:18:10] RECOVERY - wiki.edhel.online - LetsEncrypt on sslhost is OK: OK - Certificate 'edhel.online' will expire on Fri 18 Sep 2020 06:20:45 GMT +0000. [07:40:23] Reception123: needs removing [11:28:36] PROBLEM - cp8 Stunnel Http for mw7 on cp8 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:28:51] PROBLEM - cp6 Stunnel Http for mw4 on cp6 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:29:22] PROBLEM - cp8 HTTPS on cp8 is CRITICAL: HTTP CRITICAL: HTTP/1.1 503 Backend fetch failed - 4391 bytes in 0.362 second response time [11:29:57] PROBLEM - cp6 Stunnel Http for mw5 on cp6 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:30:05] PROBLEM - cp7 Stunnel Http for mw7 on cp7 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:30:32] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 8 datacenters are down: 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 51.77.107.210/cpweb, 51.89.160.142/cpweb, 2001:41d0:800:1056::2/cpweb, 2001:41d0:800:105a::10/cpweb, 51.161.32.127/cpweb, 2607:5300:205:200::17f6/cpweb [11:30:46] PROBLEM - cp8 HTTP 4xx/5xx ERROR Rate on cp8 is CRITICAL: CRITICAL - NGINX Error Rate is 80% [11:30:50] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 8 datacenters are down: 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 51.77.107.210/cpweb, 51.89.160.142/cpweb, 2001:41d0:800:1056::2/cpweb, 2001:41d0:800:105a::10/cpweb, 51.161.32.127/cpweb, 2607:5300:205:200::17f6/cpweb [11:32:53] PROBLEM - cp6 Stunnel Http for mw6 on cp6 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:33:43] RECOVERY - cp8 Stunnel Http for mw7 on cp8 is OK: HTTP OK: HTTP/1.1 200 OK - 15525 bytes in 0.333 second response time [11:33:56] RECOVERY - cp6 Stunnel Http for mw4 on cp6 is OK: HTTP OK: HTTP/1.1 200 OK - 15525 bytes in 0.004 second response time [11:34:20] RECOVERY - cp8 HTTPS on cp8 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 1834 bytes in 0.397 second response time [11:34:42] RECOVERY - cp6 Stunnel Http for mw5 on cp6 is OK: HTTP OK: HTTP/1.1 200 OK - 15525 bytes in 0.006 second response time [11:34:47] RECOVERY - cp7 Stunnel Http for mw7 on cp7 is OK: HTTP OK: HTTP/1.1 200 OK - 15525 bytes in 0.011 second response time [11:34:53] RECOVERY - cp6 Stunnel Http for mw6 on cp6 is OK: HTTP OK: HTTP/1.1 200 OK - 15533 bytes in 0.010 second response time [11:35:02] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [11:35:23] RECOVERY - cp8 HTTP 4xx/5xx ERROR Rate on cp8 is OK: OK - NGINX Error Rate is 1% [11:35:26] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [11:53:48] Hi [11:55:47] hello [11:56:57] i was checking managewiki and i saw "CreatePageUw" is allowed so it can be activated, to use this: https://www.mediawiki.org/wiki/Extension:CreatePageUw [11:56:57] [ Extension:CreatePageUw - MediaWiki ] - www.mediawiki.org [11:57:27] yes [11:58:35] Once it's on, does anything else need to be done to make it work? [11:58:50] no [11:59:06] {}{ [11:59:20] i don't see [[Special:CreatePage]] on my wiki. [11:59:37] but maybe is because my wiki autotranslates to spanish [11:59:58] Avengium: just type Special:CreatePage in the search bar [12:00:44] leads me to: https://tuscriaturas.miraheze.org/wiki/Especial:Crear_p%C3%A1gina [12:00:44] [ No existe esa página especial - Bestiario del Hypogripho ] - tuscriaturas.miraheze.org [12:01:27] that is because you didnt have it enabled Avengium [12:01:31] i enabled it for you [12:02:16] ok, thanks [12:03:33] I didn´'t see the button to apply changes in managewiki so i wasn't sure [12:10:56] Avengium: hit the submit button [12:12:54] sorry, but i don't see the submit button. [12:13:02] but thanks [12:13:03] bye [12:30:24] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNCi [12:30:25] [02miraheze/services] 07MirahezeSSLBot 03df0978a - BOT: Updating services config for wikis [12:45:14] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNCF [12:45:15] [02miraheze/services] 07MirahezeSSLBot 03e15627e - BOT: Updating services config for wikis [12:55:33] Hello Heman76! If you have any questions, feel free to ask and someone should answer soon. [12:56:16] RhinosF1 Hello. [12:56:35] Reception123 Hello. [12:58:00] RhinosF1 Hello!!! [12:58:19] revi Hello. [13:11:09] Need an crat https://meta.miraheze.org/m/4XG [13:11:10] [ Meta:Administrators' noticeboard - Miraheze Meta ] - meta.miraheze.org [13:13:37] revi: removed, thanks for all you've done over the years [13:13:41] thx :) [13:13:48] I'll probably stay here so not full gone anyway [13:13:51] fully* [13:22:08] Heman76: hi [13:23:04] revi: thanks for your service [13:23:49] :) [13:34:03] RhinosF1 Hello, i need to use Miraheze Toolforge. [13:34:24] I guess e did well [14:12:08] RhinosF1: and Paladox: check the sslhost alert from yesterday and deal with [14:12:32] Reception fixed [14:48:28] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 25.76, 20.62, 16.79 [14:50:26] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 19.21, 19.58, 16.86 [15:18:02] [02miraheze/mw-config] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/JfNRr [15:18:04] [02miraheze/mw-config] 07paladox 03fc04ed5 - Comments conflicts with CommentStream and vice versa TODO: Revert this when https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/CommentStreams/+/606820/ is merged [15:18:04] [ Gerrit Code Review ] - gerrit.wikimedia.org [15:18:05] [02mw-config] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vbvb3 [15:18:07] [02mw-config] 07paladox opened pull request 03#3120: Comments conflicts with CommentStream and vice versa - 13https://git.io/JfNRo [15:18:45] [02mw-config] 07paladox closed pull request 03#3120: Comments conflicts with CommentStream and vice versa - 13https://git.io/JfNRo [15:18:46] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNRi [15:18:48] [02miraheze/mw-config] 07paladox 039ecfe7c - Comments conflicts with CommentStream and vice versa (#3120) TODO: Revert this when https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/CommentStreams/+/606820/ is merged [15:18:48] [ Gerrit Code Review ] - gerrit.wikimedia.org [15:18:49] [02mw-config] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vbvb3 [15:18:51] [02miraheze/mw-config] 07paladox deleted branch 03paladox-patch-2 [15:19:37] miraheze/mw-config/paladox-patch-2/fc04ed5 - paladox The build has errored. https://travis-ci.org/miraheze/mw-config/builds/700597944 [16:07:47] PROBLEM - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [16:09:45] RECOVERY - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is OK: OK - Certificate 'thelonsdalebattalion.co.uk' will expire on Sun 16 Aug 2020 23:10:01 GMT +0000. [16:09:50] Hi , Hola [16:10:01] hispano76 ¿estás por ahí? [16:11:53] Hi. someone here? [16:12:06] I am [16:12:21] But I only really speak english [16:12:32] there are a lot of people in the user list and I don't know who to mention XD [16:12:46] ok, i will try to speak english [16:12:56] i have doubts with Favicons [16:13:06] What doubts? [16:13:33] i usually overthink and think in different possibilities, so i will tell some of my doubts [16:14:02] another admin (NimoStar) created a favicon of the site tuscriaturas [16:14:35] but i wanted to know how to create one and do it for myself. so i checked online [16:15:35] this web https://realfavicongenerator.net/ has a section to check how is your page favicon https://realfavicongenerator.net/favicon_checker [16:15:35] [ Favicon Generator for perfect icons on all browsers ] - realfavicongenerator.net [16:15:36] [ Favicon checker ] - realfavicongenerator.net [16:16:25] so i checked and the page says a lot of things [16:17:00] for example: [16:17:04] favicon.ico is missing some icons of recommended sizes (16x16, 32x32, 48x48) [16:17:50] and i also noticed that the default favicon is miraheze icon. that is something logical https://tuscriaturas.miraheze.org/favicon.ico [16:19:31] do you know how to solve some of the issues pointed by https://realfavicongenerator.net/favicon_checker?protocol=https&site=tuscriaturas.miraheze.org#.Xu-Impozapo [16:19:31] [ Favicon checker ] - realfavicongenerator.net [16:20:41] and another question. Can wiki admins change the favicon in https:// .miraheze.org/favicon.ico to the custom favicon or is there a need to keep the original favicon? [16:21:28] You can change your favicon [16:22:09] yes, i have one already. is called /tuscriaturaswiki/c/c5/Cabeza_Mago_Fractal_for_favicon_2.ico [16:22:41] but checking on that page https://realfavicongenerator.net/favicon_checker it puts the issue: [16:22:42] [ Favicon checker ] - realfavicongenerator.net [16:22:45] https://static.miraheze.org/tuscriaturaswiki/c/c5/Cabeza_Mago_Fractal_for_favicon_2.ico and https://tuscriaturas.miraheze.org/favicon.ico both exist and are different [16:23:03] in a red background, so i supposed is something detrimental [16:24:27] Should i adress this better on a ticket / email that is more structured or is ok with the IRC [16:24:46] Go to 'manage your wiki's additional settings' then in the 'styling' tab is place to put the link to the favicon you want to use [16:24:54] '=D I don't want to give the impression that I'm annoying and ask a lot [16:26:44] Buenas [16:26:54] Hola Hispano76 [16:28:33] no se si es que soy perfeccionista sobre un detalle pequeño, pero me han dado dudas sobre el favicon, y no se que puedo hacer para despejarlas. quizás tenga que practicar más para salir de dudas [16:33:48] hispano76 ¿te pillo ocupado? [16:34:26] Avengium: Yo no revisé nada (en otros dispositivos) cuando añadí una imagen con formato ICO en mi wiki, y parece que tienen los mismos "problemas". ¿o en que dispositivos salen mal y te gustaría arreglar? [16:35:16] (y curiosamente también tienen casi esos "problemas" con probar es.wikipedia.org) [16:35:18] en principio no he visto otros dispositivos, porque no los tengo. pero me preguntaba si esas issues que aparecen son reales o no [16:36:30] Diría que no repercute en tu wiki, solo es un detalle menor. [16:36:43] y la frase de : "favicon.ico is missing some icons of recommended sizes (16x16, 32x32, 48x48)" me hace pensar como si se necesitara un favicon más grande o se necesitara un pack de ellos. [16:37:06] vale. bueno saberlo [16:37:58] Mejor dicho, es una sugerencia pero afecta nada [16:38:07] son sugerencias* [16:38:09] Vale [16:38:40] Avengium: this channel is here for people to ask questions, so don't worry about asking a lot. [16:39:09] y me he fijado que el favicon por defecto viene eso por defecto, que no está subido mediante el sistema de archivos de la wiki. con lo que deduzco que algún dispositivo (no se cual) usará el por defecto independientemente de que yo cargue un favicon.ico con el sistema de archivos de la wiki. eso era otra duda [16:39:32] many thanks QuIRC O:3 (y) [16:40:03] :) [16:40:40] ok , bye [16:40:44] until next time [16:41:04] uh [16:41:33] We're you not done explaining? [16:41:47] s/We're/Were [16:41:47] QuIRC meant to say: Were you not done explaining? [16:44:48] i saw the IRC in the discord channel [16:45:13] QuIRC , i need to keep checking things and dispel these doubts by myself [16:46:08] ok [16:48:29] avengium: Es una configuración predeterminada en LocalSettings.php según recuerdo (creo que toma el archivo que existe en Wikimedia Commons), de la misma manera en que funciona el diseño de los wikis, Managewiki, extensiones, etc. [16:49:24] avengium: ¿me has entendido? :) [16:49:42] si. entonces esa es la razón por la que es esa imagen [16:51:10] nuestra wiki no está tan establecida como para tocar localsettings.php o subir la imagen a commons y despues cambiarla. así que dejaré el favicon de Miraheze en su lugar [16:51:25] ehm, eso último no me has entendido [16:51:46] puede que no te haya entendido [16:52:15] pero igualmente, según lo que creo que he entendido, no tocaré el archivo. así que no me hace falta comprenderlo totalmente de momento [16:53:36] avengium: Puedes cambiar el logo y el favicon mediante Special:ManageWiki/settings como lo he hecho yo. Por ejemplo https://commons.miraheze.org/wiki/Special:ManageWiki/settings#mw-section-styling que incluso permite el logo para Apple Touch Icon. [16:53:37] [ Manage this wiki's additional settings - Miraheze Commons ] - commons.miraheze.org [16:53:59] si, si actualmente tengo uno [16:54:07] https://static.miraheze.org/tuscriaturaswiki/c/c5/Cabeza_Mago_Fractal_for_favicon_2.ico [16:54:50] pero lo puso otro admin. quizás lo cambie en Special:ManageWiki [16:56:25] Sí, ya la mayoría de extensiones, skins, espacios de nombres, grupos de usuarios, configuraciones como logos, notificaciones, etc ya se realizan en ManageWiki. [16:56:41] avengium: https://meta.miraheze.org/wiki/ManageWiki [16:56:41] [ ManageWiki - Miraheze Meta ] - meta.miraheze.org [16:57:29] si. me gustó ver la enorme variedad de cosas que hay en managewiki [16:57:38] que bien :) [16:57:53] voy a dejar esto abierto en ausente aunque siga a otras cosas [16:58:04] ok [17:38:28] would someone please explain why sigmabot is no longer opped? [17:52:06] https://meta.miraheze.org/w/index.php?title=List_of_globally_banned_users&diff=110335&oldid=99987 [17:52:06] [ Difference between revisions of "List of globally banned users" - Miraheze Meta ] - meta.miraheze.org [17:54:08] "details not available" got it [17:54:09] that clears it up [18:01:12] >  https://meta.miraheze.org/w/index.php?title=List_of_globally_banned_users&diff=110335&oldid=99987 Thanks...I was wondering if EK was the operator of the SigmaBot. Did SigmaBot perform any other functions besides acting as an IRC<-->Discord relay? [18:01:13] [ Difference between revisions of "List of globally banned users" - Miraheze Meta ] - meta.miraheze.org [18:01:54] SigmaBot was used for moderation purposes, and isn't the relay bot [18:02:41] >  SigmaBot was used for moderation purposes, and isn't the relay bot @Miraheze-IRC Ah, okay, thanks. So what's the new IRC chat moderation bot? (Sorry not on IRC a lot. lol) [18:02:49] there isn't one yet [18:03:02] sigma was responsible for banning people, but is now deopped and kicked [18:03:50] |  there isn't one yet Oh. Thanks. That makes sense. I'm surprised there isn't an out-of-the-box open-source IRC chat moderation bot that could be implemented instantly. [18:04:08] ChanServ exists [18:04:14] that's the easiest [18:04:14] just that everyone has different ideas of what a bot should do [18:04:20] Void-bot has a set of modules for similar purposes, but I still need to tweak the config and make sure it's not picking up on things it shouldn't [18:05:02] moderation bots include ChanServ, eir, Sigyn, and Void-bot [18:05:32] Ah, thanks. I would say keep things simple; no blacklisted spam websites, no repeatedly talking in ALL CAPS LOCK, and no saying the same thing more than three times in a short span of time. [18:05:53] the first three are operated by freenode (iirc), and Void-bot is my own project [18:06:07] ah [18:06:59] curious...when I'm chatting in the IRC channel via Discord, is my IP passed through, or does it show up as the Discord server IP? [18:07:10] or do I come through under the bot's handle? [18:07:22] IRC see only the relay bot [18:07:39] ah [18:08:35] then I guess I don't really need a cloak then...I can just chat via the #irc-relay channel. I wish TestWiki had a Discord server, though, or at least a miscellaneous channel on this server. 😛 [18:09:21] maybe we can link the irc channel to discord [18:10:35] Voidwalker: I rescued all the code for Sigma, MH-WikiBot & Sygnal [18:11:00] @Doug: We can set it up, only Zppix can add a relay though. [18:11:22] Voidwalker: we could just put MH-Discord bot in the testwiki channel. [18:11:37] won't do anything if it hasn't been configured [18:11:44] ^ [18:11:51] Only Zppix can do that afaik [18:12:03] Ok [18:12:10] would like to take a look at how that code works (from those other bots) [18:12:36] Voidwalker: will email it later or if SPF|Cloud approves my access request add it to phab [18:12:57] @RhinosF1 and @Void Thanks. That idea sounds good. Would it be in the #irc-relay Discord channel, though? I'd prefer to have an #irc-relay-testwiki Discord channel, to separate the conversations. [18:13:14] that's how it works, yeah [18:13:25] I'd imagine that they would make a separate channel in Discord [18:14:04] It can be called anything [18:14:15] Yeah, that sounds simple enough. I'm sure @Zppix would be on board with that...assuming IRC chat bots don't use too much bandwidth. Is he self-hosting these on his computer? [18:14:37] Not on his computer, no [18:14:51] * RhinosF1 isn't 100% sure on the current host [18:14:56] ah, okay, that''s good...Miraheze server? [18:15:17] We don't have any official bot hosting [18:15:20] Seems like within the scope of the project to Miraheze to host on one of their VPSes. [18:15:25] Oh. [18:15:49] iirc, it's hosted on Heroku, or some other free hosting platform, and does suffer from bandwidth issues [18:15:53] It's not impossible for us to do [18:16:39] ah [18:19:50] There's no resources though for it [18:28:37] Hi [18:29:01] How can i expand the number of days in recent changes to reach more than 30 days? [18:32:53] special:ManageWiki/settings#mw-section-recentchanges [18:33:18] >  How can i expand the number of days in recent changes to reach more than 30 days? @Miraheze-IRC Good question. It seems like something that should be configurable in the same way other extensions can be customized, but I'm not sure if that's the case here. Ah, looks like it is. Thanks, @Hispano76. 🙂 [18:34:54] Avengium: alguna duda? [18:35:57] no, voy a probar a añadir la extensión de 60 días [18:36:55] pero igual no valdrá para revisar una wiki inactiva porque tendrían que haberlo puesto los burocratas anteriores, jeje [18:37:43] he visto que es un desplegable [18:38:31] y las opciones pasan de 30 a 180 que es maximo que se pone en el primer campo. [18:39:26] pero MH-Discord tuvo una buena idea. quizás se podrian añadir las franjas de 60 y 90 días desde Miraheze para que se pudiera elegir [18:40:28] english: but MH-Discord had a good idea. perhaps the 60 and 90 day options could be added by Miraheze admins so that you can choose those sections of time [18:44:47] 60 days is 5,184,000 seconds [18:51:20] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JfNVI [18:51:21] [02miraheze/mediawiki] 07paladox 03b37c36f - Update PortableInfobox [18:54:30] [02miraheze/MirahezeMagic] 07paladox pushed 031 commit to 03paladox-patch-3 [+0/-0/±1] 13https://git.io/JfNVY [18:54:32] [02miraheze/MirahezeMagic] 07paladox 031a16501 - Fix "Trying to get property 's_data' of non-object" [18:54:33] [02MirahezeMagic] 07paladox created branch 03paladox-patch-3 - 13https://git.io/fQRGX [18:54:35] [02MirahezeMagic] 07paladox opened pull request 03#129: Fix "Trying to get property 's_data' of non-object" - 13https://git.io/JfNVO [18:55:27] where i should go to leave an idea for an implementation or new option? [18:55:54] [02MirahezeMagic] 07paladox closed pull request 03#129: Fix "Trying to get property 's_data' of non-object" - 13https://git.io/JfNVO [18:55:55] [02miraheze/MirahezeMagic] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNVZ [18:55:57] [02miraheze/MirahezeMagic] 07paladox 03184b790 - Fix "Trying to get property 's_data' of non-object" (#129) [18:56:23] [02MirahezeMagic] 07paladox deleted branch 03paladox-patch-3 - 13https://git.io/fQRGX [18:56:24] [02miraheze/MirahezeMagic] 07paladox deleted branch 03paladox-patch-3 [18:57:07] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JfNVc [18:57:09] [02miraheze/mediawiki] 07paladox 03365b108 - Update MirahezeMagic [18:59:48] PROBLEM - mw4 Puppet on mw4 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [19:00:06] PROBLEM - mw5 Puppet on mw5 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [19:01:19] PROBLEM - mw6 Puppet on mw6 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [19:01:31] PROBLEM - mw7 Puppet on mw7 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 4 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [19:01:39] paladox: ^ [19:02:09] yes, always happens after [19:02:11] Jun 21 18:57:30 mw5 puppet-agent[28724]: (/Stage[main]/Mediawiki/Git::Clone[MediaWiki core]/Exec[git_pull_MediaWiki core]/returns) change from 'notrun' to ['0'] failed: Command exceeded timeout (corrective) [19:02:45] paladox: puppet always failing after a deploy doesnt sound healthy [19:03:07] i've increased the git command timeout in the passed but John objected to it [19:03:12] (so reverted) [19:04:18] paladox: hmm, if I don't see him today again, I'll file a task. [19:05:20] RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [19:05:40] RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [19:05:44] Not doing anything doesnt sound like a long term solution [19:05:48] RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [19:06:10] RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [19:27:45] PROBLEM - wiki.scvo.org - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.scvo.org' expires in 15 day(s) (Tue 07 Jul 2020 19:25:36 GMT +0000). [19:29:53] paladox: will you disable https://phabricator.miraheze.org/herald/query/y1NeMju_R4Rp/#R [19:29:54] [ ☿ Query: Advanced Search ] - phabricator.miraheze.org [19:29:59] Reception123: ^ [19:30:08] i cannot disable it [19:30:13] since the users been disabled [19:30:22] so the rules is infact already not working. [19:30:24] paladox: usually it's done by DB [19:30:28] paladox: is there not a script [19:30:46] but yes if the user is disabled it should already not be functional so there's no need to disable via db [19:31:15] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNwA [19:31:16] [02miraheze/ssl] 07MirahezeSSLBot 03959461e - Bot: Update SSL cert for wiki.scvo.org [19:31:45] Reception123: hmm [19:32:02] https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/602951/3/modules/admin/data/data.yaml might be helpful [19:32:02] [ Gerrit Code Review ] - gerrit.wikimedia.org [19:32:23] But if they soft disable on acc disable then it's fine [19:37:07] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JfNrk [19:37:09] [02miraheze/mediawiki] 07paladox 0358f73ad - Update CommentStreams [19:37:22] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNrL [19:37:23] [02miraheze/mw-config] 07paladox 03904c67c - Revert "Comments conflicts with CommentStream and vice versa (#3120)" This reverts commit 9ecfe7cfd73323e6d96d7bafb8231e3464f1e9a9. [19:38:27] PROBLEM - wiki.cloudytheology.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.cloudytheology.com' expires in 15 day(s) (Tue 07 Jul 2020 19:36:15 GMT +0000). [19:38:59] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNrs [19:39:00] [02miraheze/ssl] 07MirahezeSSLBot 03fd39458 - Bot: Update SSL cert for wiki.cloudytheology.com [19:42:26] RECOVERY - wiki.cloudytheology.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.cloudytheology.com' will expire on Sat 19 Sep 2020 18:38:51 GMT +0000. [19:43:40] RECOVERY - wiki.scvo.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.scvo.org' will expire on Sat 19 Sep 2020 18:31:08 GMT +0000. [19:45:45] PROBLEM - wiki.xfbs.net - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.xfbs.net' expires in 15 day(s) (Tue 07 Jul 2020 19:42:05 GMT +0000). [19:47:46] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfNrB [19:47:48] [02miraheze/ssl] 07MirahezeSSLBot 03d9074d8 - Bot: Update SSL cert for wiki.xfbs.net [19:53:54] RECOVERY - wiki.xfbs.net - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.xfbs.net' will expire on Sat 19 Sep 2020 18:47:40 GMT +0000. [20:16:55] can we get rid of these stupid bots and make #miraheze-logs instead [20:17:00] this channel should be for actual discussions [20:23:00] I've been thinking about re-ordering some of our channels for a while now, might propose something similar [20:46:30] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JfN6U [20:46:32] [02miraheze/mediawiki] 07paladox 031d2e3ae - Revert "Update PortableInfobox" This reverts commit b37c36f5aa1455d8fe067309ff2375e90289669c. [20:54:24] paladox: https://phabricator.miraheze.org/T5791 [20:54:24] [ ⚓ T5791 Search is not working!!! ] - phabricator.miraheze.org [20:55:03] oh bugs [20:55:25] paladox: what? [20:55:36] 2020-06-21 20:09:51 mw4 dreamsitwiki: [4bd18def4cfbd0ca059ab210] /w/index.php?search=&search=nobreak&title=Special%3ASearch&go=Go TypeError from line 331 of /srv/mediawiki/w/extensions/CommentStreams/includes/CommentStreamsHooks.php: Argument 3 passed to MediaWiki\Extension\CommentStreams\CommentStreamsHooks::showSearchHitTitle() must be an instance of MediaWiki\Extension\CommentStreams\SearchResult, instance of SqlSearchResult given, called in [20:55:36] /srv/mediawiki/w/includes/Hooks.php on line 174 [20:57:27] paladox: that's your update [20:57:37] yes [20:57:39] i know [20:57:57] Assiging task to you [20:58:11] You'll have to get a quick fix or revert [21:02:27] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 22.27, 17.45, 15.20 [21:04:32] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 18.73, 17.52, 15.48 [21:06:10] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JfN6y [21:06:12] [02miraheze/mediawiki] 07paladox 03933f3ea - Update CommentStreams [22:16:03] paladox, Reception123, Zppix, SPF|Cloud, Voidwalker: around? [22:16:08] yes [22:16:19] am now [22:18:05] texas/examknow is back online as well [22:18:14] not in this channel but online in general [22:18:43] Naleksuh: well aware [22:18:54] okay so whats up? [22:18:54] I thought you wanted to talk to me. [22:18:54] no i just said i was doing stuff onwiki and then you said " Naleksuh: I am aware. If you would like to discuss this matter further, please do it in query." [22:18:54] Oh okay. [22:18:54] what did you mean that you were aware of? [22:18:55] Nothing. [22:18:57] and you also wanted to discuss "this matter" furthur without knowing what "this matter" what [22:18:59] or why it should be private [22:19:00] Voidwalker: paladox is passing to -staff [22:19:01] I did not wish to discuss it. If you did not already know, then you will not be finding out. [22:19:13] RhinosF1 why did you need to ping him for that? [22:19:20] seriously [22:19:39] so he knows that i've seen his message [22:19:50] but void knows already? [22:20:35] ok [22:20:40] * RhinosF1 tired [22:30:31] Miraheze has a strong privacy stance (ex. we will never run adverts) [22:30:39] https://meta.miraheze.org/wiki/Requests_for_Comment/NordVPN [22:30:41] [ Requests for Comment/NordVPN - Miraheze Meta ] - meta.miraheze.org [22:41:10] Hello koopa-troopa! If you have any questions, feel free to ask and someone should answer soon. [22:41:58] RHINOSF1 IS GAY WITH RECEPTION123! TEXAS IS GAY WITH AMANDANP! HISPANO76 IS GAY WITH VOID! AND SIGMABOTS SLEEPS WITH SIGN! [22:44:37] RHINOSF1 IS GAY WITH RECEPTION123! TEXAS IS GAY WITH AMANDANP! HISPANO76 IS GAY WITH VOID! AND SIGMABOTS SLEEPS WITH SIGN! [23:06:00] oh huh embeds are enabled here [23:06:01] fun [23:14:58] is anyone here known as 松 on-wiki? [23:30:29] PROBLEM - cp8 Disk Space on cp8 is WARNING: DISK WARNING - free space: / 2115 MB (10% inode=93%);