[01:45:05] The talk pages used on the All The Tropes seems to be not very good. Among other things, there is no preview, and the keyboard commands don't seems to work. There is also some messages about deprecated stuff in the console. [01:45:43] ¿example? [01:46:16] It is the system used by all of the talk pages, and is not specific to a single one, I think. [01:46:56] ALT+SHIFT+P and ALT+SHIFT+S don't work like it does for editing a normal page. [01:47:35] It's because they use Flow and that's how it's configured [01:48:13] Is that a problem with Flow or with the configuration of Flow? [01:49:16] This is how Flow is configured, I'm not aware of any other way to leave messages in discussions [01:50:30] I think it is no good that there is no preview and that the keyboard commands don't work. [01:51:00] You could edit a user subpage by writing your message without saving it and then put the message in the corresponding discussion, something I do in other projects that don't have the settings I want. [01:53:13] zzo38: Anything else? [01:54:05] OK, that would work, but that seems like messy to me. Is there a way to fix it by use of the user JavaScript codes? I suppose the script can add the keyboard commands is not too difficult (possibly also add absolute dates; I prefer those to the relative ones), and maybe add a iframe if a preview is requested. [01:54:36] Is there some MediaWiki API which will create a preview by itself without the editing form and that stuff, which can be used for this purpose? [01:55:58] (I know JavaScript programming, but I don't know much about the DOM and API stuff) [01:57:31] I'm sorry, I'm not sure that's possible. Other colleagues might know [01:58:24] OK, let's see if anyone else answers [02:01:48] ok :) [02:04:52] Flow is more than a little weird, and I don't know how to do page previews with the API, although I do think it is possible [02:05:31] I'm pretty sure the depreciation warnings you see in the console window have to do with the old JS gadgets that the wiki uses that haven't been updated in over a year [02:06:56] I only see those deprecation warnings on talk pages, it seems [02:07:18] But in any case, the deprecation warnings aren't my problem; I just thought I should mention them. [02:07:49] Oh, that's interesting, maybe I'll take a look into where those are coming from [02:41:16] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JexHG [02:41:18] [02miraheze/mediawiki] 07paladox 033eb0210 - Update Comments [05:56:22] I found out a way to do it; maybe it will be useful to other users too. https://allthetropes.org/wiki/User:Zzo38/cologneblue.js [05:56:24] [ User:Zzo38/cologneblue.js - All The Tropes ] - allthetropes.org [05:57:14] Do you think it is good? [06:09:14] I also think that another thing that would be good to have for discussion forum would be NNTP. [06:26:39] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 3250 MB (13% inode=94%); [08:08:02] [02landing] 07AlirezaIvaz opened pull request 03#25: Add Persian Support - 13https://git.io/JexFj [08:12:07] [02landing] 07RhinosF1 reviewed pull request 03#25 commit - 13https://git.io/JexbT [10:08:48] PROBLEM - db4 Disk Space on db4 is CRITICAL: DISK CRITICAL - free space: / 21974 MB (5% inode=95%); [10:24:06] JohnLewis: https://phabricator.miraheze.org/T5049 [10:24:07] [ ⚓ T5049 The rename progress for my Miraheze account (FireBarrier101) ] - phabricator.miraheze.org [10:24:12] Reception123: ^ [10:24:53] No access atm but will look when possible if no one does (will be a long while though) [10:25:40] Reception123: ok, it's not a no db thing so not sure [10:28:43] .mh SAL [10:28:44] https://meta.miraheze.org/wiki/SAL [10:29:59] Reception123: can you remember why it failed first time (https://phabricator.miraheze.org/T5049#96260) [10:30:00] [ ⚓ T5049 The rename progress for my Miraheze account (FireBarrier101) ] - phabricator.miraheze.org [11:31:29] PROBLEM - cp4 Stunnel Http for mw3 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:32:07] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 5 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [11:32:14] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [11:32:24] PROBLEM - cp4 Stunnel Http for mw1 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:32:42] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw1 [11:32:59] PROBLEM - cp2 Stunnel Http for mw1 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:33:24] RECOVERY - cp4 Stunnel Http for mw3 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 15204 bytes in 0.129 second response time [11:34:22] RECOVERY - cp4 Stunnel Http for mw1 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 15197 bytes in 0.013 second response time [11:34:55] RECOVERY - cp2 Stunnel Http for mw1 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15203 bytes in 1.731 second response time [11:36:47] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 7 backends are healthy [11:40:27] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [11:40:28] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 2 backends are down. mw1 mw2 [11:40:41] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [11:40:44] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 1 backends are down. mw1 [11:41:32] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:42:41] PROBLEM - cp4 Stunnel Http for mw1 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:45:15] PROBLEM - cp2 Stunnel Http for mw3 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:45:40] PROBLEM - mw3 MediaWiki Rendering on mw3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [11:45:49] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 7 backends are healthy [11:47:08] RECOVERY - cp4 Stunnel Http for mw1 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 15203 bytes in 8.637 second response time [11:47:31] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 3 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [11:47:31] RECOVERY - cp2 Stunnel Http for mw3 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15198 bytes in 0.293 second response time [11:47:54] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 107.191.126.23/cpweb, 81.4.109.133/cpweb [11:48:29] PROBLEM - cp2 Stunnel Http for mw1 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:49:32] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [11:50:05] RECOVERY - mw3 MediaWiki Rendering on mw3 is OK: HTTP OK: HTTP/1.1 200 OK - 18611 bytes in 0.837 second response time [11:50:07] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 2 backends are down. mw1 mw2 [11:50:31] RECOVERY - cp2 Stunnel Http for mw1 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15197 bytes in 0.411 second response time [11:53:38] PROBLEM - cp4 Stunnel Http for mw2 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:53:48] PROBLEM - cp3 Stunnel Http for mw2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:54:36] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [11:55:08] paladox: 6 [11:55:18] S/6/^ [11:55:19] RhinosF1 meant to say: paladox: ^ [11:57:34] PROBLEM - cp2 Stunnel Http for mw2 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:59:33] RECOVERY - cp2 Stunnel Http for mw2 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15190 bytes in 1.225 second response time [11:59:56] RECOVERY - cp3 Stunnel Http for mw2 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15198 bytes in 0.474 second response time [11:59:58] RECOVERY - cp4 Stunnel Http for mw2 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 15198 bytes in 0.004 second response time [12:03:01] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 1 datacenter is down: 2a00:d880:5:8ea::ebc7/cpweb [12:03:03] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 107.191.126.23/cpweb, 128.199.139.216/cpweb [12:04:30] PROBLEM - cp2 Stunnel Http for mw2 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:04:40] PROBLEM - cp3 Stunnel Http for mw2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:05:41] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 6 backends are healthy [12:09:04] RECOVERY - cp3 Stunnel Http for mw2 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15190 bytes in 5.215 second response time [12:09:07] RECOVERY - cp2 Stunnel Http for mw2 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15204 bytes in 6.306 second response time [12:09:44] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 7 backends are healthy [12:10:03] PROBLEM - cp2 Stunnel Http for mw3 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:10:04] PROBLEM - cp4 Stunnel Http for mw3 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:10:30] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 1 backends are down. mw2 [12:13:39] PROBLEM - cp3 Stunnel Http for mw2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:13:50] PROBLEM - cp2 Stunnel Http for mw2 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:14:16] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 2 backends are down. mw1 mw2 [12:14:41] PROBLEM - cp3 Stunnel Http for mw1 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:18:05] RECOVERY - cp2 Stunnel Http for mw2 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15204 bytes in 4.865 second response time [12:18:08] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [12:18:49] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 6 backends are healthy [12:22:05] RECOVERY - cp3 Stunnel Http for mw2 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15198 bytes in 0.506 second response time [12:22:28] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 4 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb [12:22:33] PROBLEM - test1 MediaWiki Rendering on test1 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [12:22:38] PROBLEM - cp2 Stunnel Http for mw2 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:22:50] PROBLEM - cp4 Stunnel Http for mw2 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:23:04] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 1 backends are down. mw1 [12:23:44] RECOVERY - cp3 Stunnel Http for mw1 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15203 bytes in 6.184 second response time [12:24:52] RECOVERY - test1 MediaWiki Rendering on test1 is OK: HTTP OK: HTTP/1.1 200 OK - 18611 bytes in 1.914 second response time [12:25:01] PROBLEM - cp2 Stunnel Http for mw1 on cp2 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 309 bytes in 0.294 second response time [12:25:06] RECOVERY - cp2 Stunnel Http for mw3 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15198 bytes in 0.293 second response time [12:25:21] RECOVERY - cp4 Stunnel Http for mw3 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 15198 bytes in 0.026 second response time [12:26:34] PROBLEM - mw1 MediaWiki Rendering on mw1 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [12:26:45] PROBLEM - cp3 Stunnel Http for mw2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:26:57] RECOVERY - cp2 Stunnel Http for mw1 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15197 bytes in 0.452 second response time [12:28:43] RECOVERY - mw1 MediaWiki Rendering on mw1 is OK: HTTP OK: HTTP/1.1 200 OK - 18611 bytes in 1.097 second response time [12:29:01] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [12:29:06] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [12:29:21] RECOVERY - cp2 Stunnel Http for mw2 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15204 bytes in 4.093 second response time [12:29:28] RECOVERY - cp4 Stunnel Http for mw2 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 15198 bytes in 0.006 second response time [12:29:32] PROBLEM - mw3 MediaWiki Rendering on mw3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [12:32:03] PROBLEM - cp3 Stunnel Http for mw1 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:33:10] RECOVERY - cp3 Stunnel Http for mw2 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15198 bytes in 1.755 second response time [12:36:11] RECOVERY - mw3 MediaWiki Rendering on mw3 is OK: HTTP OK: HTTP/1.1 200 OK - 18611 bytes in 0.821 second response time [12:36:25] RECOVERY - cp3 Stunnel Http for mw1 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15189 bytes in 1.547 second response time [12:37:52] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 7 backends are healthy [12:37:53] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 6 backends are healthy [12:37:56] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 6 backends are healthy [12:41:41] PROBLEM - cp2 Stunnel Http for mw2 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:41:53] PROBLEM - cp3 Stunnel Http for mw2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:41:57] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 107.191.126.23/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [12:42:23] PROBLEM - cp3 Stunnel Http for mw3 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:42:29] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 1 backends are down. mw3 [12:42:30] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw3 [12:42:33] PROBLEM - cp4 Stunnel Http for mw3 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:42:35] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 1 backends are down. mw3 [12:44:10] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [12:44:11] PROBLEM - cp4 Stunnel Http for mw1 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [12:44:35] RECOVERY - cp3 Stunnel Http for mw3 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15204 bytes in 0.821 second response time [12:45:52] RECOVERY - cp2 Stunnel Http for mw2 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15204 bytes in 1.743 second response time [12:46:02] RECOVERY - cp3 Stunnel Http for mw2 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15204 bytes in 4.707 second response time [12:46:09] RECOVERY - cp4 Stunnel Http for mw1 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 15197 bytes in 0.004 second response time [12:46:52] RECOVERY - cp4 Stunnel Http for mw3 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 15198 bytes in 0.005 second response time [12:49:04] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 6 backends are healthy [12:50:37] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 6 backends are healthy [12:50:40] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 7 backends are healthy [12:51:08] I'd like to suggest moving icinga-miraheze to a dedicated channel, something like #miraheze-tech [12:52:25] quirc: you're not the first to say that [12:54:07] RhinosF1: It would make having a conversation in here easier. [12:54:38] yep [13:03:32] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JexhG [13:03:33] [02miraheze/puppet] 07paladox 03eb02058 - Update php.pp [13:04:36] paladox: there's a stuck rename [13:05:06] I’m currently mobile [13:05:36] ok [13:07:14] [02puppet] 07paladox closed pull request 03#1171: mediawiki: Redirect wiki.miraheze.org to meta.miraheze.org - 13https://git.io/JeNQ9 [13:07:18] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-10 [13:07:19] [02puppet] 07paladox deleted branch 03paladox-patch-10 - 13https://git.io/vbiAS [13:15:54] Im mobile too otherwise i’d try to help [13:16:10] Afternoon Zppix [13:16:48] Morning heh [15:37:35] PROBLEM - cp2 Stunnel Http for mw3 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [15:37:45] PROBLEM - cp2 Stunnel Http for misc2 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [15:39:29] RECOVERY - cp2 Stunnel Http for mw3 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 15198 bytes in 0.293 second response time [15:39:43] RECOVERY - cp2 Stunnel Http for misc2 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 43687 bytes in 0.438 second response time [16:20:46] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2645 MB (10% inode=94%); [16:25:43] miraheze no work [16:25:48] hum [16:31:48] other sites work well for me [16:31:51] hispano76: how? [16:32:58] When I access a wiki it stays loaded too long, much longer than usual. [16:34:15] That doesn't happen on Wikimedia or Wikia [16:35:10] Does it work for you? (metawiki) [16:35:25] RhinosF1: [16:35:47] hispano76: let me look [16:36:33] hispano76: looks fine from here [16:36:35] paladox: ? [16:38:46] Um, I'll still check the browser. [16:41:31] RhinosF1 ? [16:42:07] paladox: meta slow for hispano and https://phabricator.miraheze.org/T5054 [16:42:07] hispano76 i guess you hit lizardfs6 [16:42:08] [ ⚓ T5054 Renew Various SSL certs ] - phabricator.miraheze.org [16:43:00] according to the nginx dashbioard, mw* have not been slow in over an hour [16:43:04] so it has to be lizardfs6 [16:45:50] [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JepkR [16:45:52] [02miraheze/dns] 07paladox 031de56ec - Add acme challenge for m.miraheze.org [16:47:01] miraheze/dns/master/1de56ec - paladox The build has errored. https://travis-ci.org/miraheze/dns/builds/632358690 [16:48:00] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jepk2 [16:48:01] [02miraheze/ssl] 07paladox 036eea03c - Renew m.miraheze.org [16:49:02] [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JepkV [16:49:04] [02miraheze/dns] 07paladox 03e5c8676 - Add acme challenge for orain.org [16:50:00] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jepkw [16:50:01] [02miraheze/ssl] 07paladox 03fa04a9a - Renew orain.org [16:50:14] miraheze/dns/master/e5c8676 - paladox The build has errored. https://travis-ci.org/miraheze/dns/builds/632360256 [16:52:02] RECOVERY - m.miraheze.org - LetsEncrypt on sslhost is OK: OK - Certificate 'm.miraheze.org' will expire on Thu 02 Apr 2020 03:46:59 PM GMT +0000. [16:52:27] [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jepki [16:52:29] [02miraheze/dns] 07paladox 039e29dd1 - Add acme challenge to miraheze.com [16:52:33] paladox: thx, might want to kick travis [16:53:07] Althiugh m.miraheze.org is a 404 and surely can go on *.miraheze.org [16:53:30] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jepk1 [16:53:31] [02miraheze/ssl] 07paladox 03f2f426a - Renew miraheze.com [16:53:37] miraheze/dns/master/9e29dd1 - paladox The build has errored. https://travis-ci.org/miraheze/dns/builds/632361763 [16:54:26] [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JepkM [16:54:27] [02miraheze/dns] 07paladox 035694a69 - Add acme challenge to miraheze.wiki [16:55:31] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jepky [16:55:33] [02miraheze/ssl] 07paladox 03e283c97 - Renew miraheze.wiki [16:55:34] miraheze/dns/master/5694a69 - paladox The build has errored. https://travis-ci.org/miraheze/dns/builds/632362714 [16:59:05] Well, it's working already. paladox RhinosF1 [17:01:44] RECOVERY - orain.org - LetsEncrypt on sslhost is OK: OK - Certificate 'orain.org' will expire on Thu 02 Apr 2020 03:49:41 PM GMT +0000. [17:01:54] RECOVERY - miraheze.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'miraheze.wiki' will expire on Thu 02 Apr 2020 03:55:14 PM GMT +0000. [17:02:40] RECOVERY - miraheze.com - LetsEncrypt on sslhost is OK: OK - Certificate 'miraheze.com' will expire on Thu 02 Apr 2020 03:53:10 PM GMT +0000. [17:02:44] RECOVERY - poserdazfreebies.orain.org - LetsEncrypt on sslhost is OK: OK - Certificate 'orain.org' will expire on Thu 02 Apr 2020 03:49:41 PM GMT +0000. [17:02:58] RECOVERY - allthetropes.orain.org - LetsEncrypt on sslhost is OK: OK - Certificate 'orain.org' will expire on Thu 02 Apr 2020 03:49:41 PM GMT +0000. [17:03:35] RECOVERY - meta.orain.org - LetsEncrypt on sslhost is OK: OK - Certificate 'orain.org' will expire on Thu 02 Apr 2020 03:49:41 PM GMT +0000. [18:01:30] Sorry, because sometimes it takes a long time to log in on other wikis or they never do, when I log in on metawiki for example? on Wikimedia it takes up to 30 seconds but here it's not the same. paladox RhinosF1 [18:01:41] yup [18:01:47] wikimedia have powerful servers [18:02:15] (not to mention they have a heap more servers then us :)) [18:02:32] we need to increase our capacity. [18:04:40] Okay, I wanted to know why. thanks paladox :) [18:35:20] PROBLEM - wiki.8b8t.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [18:37:21] RECOVERY - wiki.8b8t.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.8b8t.com' will expire on Fri 21 Feb 2020 05:25:26 AM GMT +0000. [18:43:47] PROBLEM - wiki.8b8t.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [18:49:29] Whats happening there? ^ [19:09:10] who knows [19:13:07] Whys paladox klined [19:13:24] pff [19:14:29] that happened to other users on other channels [19:14:38] Great [19:15:21] freenode took the liberty of k-lining a whole bunch of xshellz users [19:15:40] it was an automated open proxy scan that xshellz apparently failed [19:15:57] a whole bunch of users got disconnected, including my backup ZNC instance, which uses xshellz [19:16:46] shell.xshellz.com is currently banned [19:17:00] k6ka: how fantastic [19:19:23] k6ka: ive asked in #freenode [19:21:06] I'll contact him on Discord [19:35:58] RECOVERY - wiki.8b8t.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.8b8t.com' will expire on Fri 21 Feb 2020 05:25:26 AM GMT +0000. [19:38:44] paladox: welcome back [19:40:19] thanks [19:42:04] paladox: did xshellz get unbanned or are you on another host? [19:42:15] xshellz was never banned [19:42:37] paladox: thats what k6ka said [19:42:46] oh [19:42:54] 19:16:46 shell.xshellz.com is currently banned [19:43:13] paladox: you got K-Lined, likely that’s why [19:43:20] oh [19:43:40] Some auto proxy fail [19:43:56] the k-line was lifted, so yes, it was unbanned [19:44:25] thanks [19:45:43] Thanks k6ka [19:52:50] PROBLEM - wiki.8b8t.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:56:53] RECOVERY - wiki.8b8t.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.8b8t.com' will expire on Fri 21 Feb 2020 05:25:26 AM GMT +0000. [20:01:15] PROBLEM - wiki.8b8t.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [20:03:14] RECOVERY - wiki.8b8t.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.8b8t.com' will expire on Fri 21 Feb 2020 05:25:26 AM GMT +0000. [20:30:35] PROBLEM - wiki.8b8t.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [20:34:38] RECOVERY - wiki.8b8t.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.8b8t.com' will expire on Fri 21 Feb 2020 05:25:26 AM GMT +0000. [20:48:43] Hello Skamp! If you have any questions, feel free to ask and someone should answer soon. [20:51:31] I think I'm missing something. I foolowed the guide on how to install CreateWiki and ManageWiki on mediawiki.org and I'm getting this error when trying to edit settings on a wiki: `Error from line 101 of .../extensions/ManageWiki/includes/specials/SpecialManageWiki.php: Call to a member function getFormSections() on bool`. What am I doing wrong? [20:51:57] Do I have to use $wgSharedDB or something? [20:52:47] The only page I can view is core - Special:ManageWiki/core/testwiki [20:54:10] paladox: JohnLewis SPF|Cloud see [20:54:39] Skamp hi, which version of mediawiki are you running? [20:55:11] 1.34.0 [20:56:40] hmm [20:57:12] Did you set the config [20:57:22] yes [20:57:48] https://github.com/miraheze/mw-config/blob/master/ManageWikiExtensions.php and https://github.com/miraheze/mw-config/blob/master/ManageWikiSettings.php [20:57:49] [ mw-config/ManageWikiExtensions.php at master · miraheze/mw-config · GitHub ] - github.com [20:57:51] [ mw-config/ManageWikiSettings.php at master · miraheze/mw-config · GitHub ] - github.com [20:59:01] it is required to set the settings yourself? [21:01:02] yupohh [21:01:03] ohh [21:01:14] Did you setup cw_wikis table? [21:01:25] does it include the wiki & also 'default'? [21:01:31] I have set the $wgManageWikiSettings to `'wgDefaultTheme' => [ [21:01:35] (Monobook only)' => 'stellarbook', [21:01:42] and still nothing [21:01:50] let me see [21:02:41] and I know that it should be an array, I'm saying that wgDefaultTheme is the only item in it [21:03:17] the cw_wikis table only includes one wiki that i created through Special:CreateWiki [21:04:50] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/JepO6 [21:04:52] [02miraheze/ManageWiki] 07paladox 039a02ddb - Fix "Call to a member function getFormSections() on bool" Sometimes $formFactory->getForm can return a bool, so handle it correctly. [21:04:53] [02ManageWiki] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vpSns [21:04:55] [02ManageWiki] 07paladox opened pull request 03#129: Fix "Call to a member function getFormSections() on bool" - 13https://git.io/JepOi [21:05:05] Skamp could you try ^ please? [21:05:20] yup, one second [21:05:58] Looks like your either hitting https://github.com/miraheze/ManageWiki/blob/master/includes/formFactory/ManageWikiFormFactory.php#L31 or the one below. [21:05:59] [ ManageWiki/ManageWikiFormFactory.php at master · miraheze/ManageWiki · GitHub ] - github.com [21:06:17] paladox: absolutely do not merge that, make a clean fix or don't fix at all [21:07:03] Now I'm getting "That wiki does not exist. [21:07:09] Now I'm getting "That wiki does not exist." message [21:07:30] oops, sorry [21:08:45] How can I edit the 'default' wiki? Did I miss a step when setting up the extension? [21:10:06] Skamp getting closer now [21:17:20] PROBLEM - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is WARNING: WARNING - NGINX Error Rate is 40% [21:19:03] Do I have to run some maintenance script? [21:19:21] RECOVERY - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is OK: OK - NGINX Error Rate is 35% [21:21:16] Skamp yeh [21:21:42] https://github.com/miraheze/CreateWiki/blob/master/maintenance/DBListGenerator.php [21:21:43] [ CreateWiki/DBListGenerator.php at master · miraheze/CreateWiki · GitHub ] - github.com [21:22:36] just ran it. Got no output [21:23:17] or did i have to run it just after instalation? [21:23:30] [02ManageWiki] 07paladox synchronize pull request 03#129: Fix "Call to a member function getFormSections() on bool" - 13https://git.io/JepOi [21:23:32] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/Jep38 [21:23:33] [02miraheze/ManageWiki] 07paladox 035635557 - Update SpecialManageWiki.php [21:24:00] Skamp Did you set wgCreateWikiDBDirectory? [21:24:53] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/Jep34 [21:24:55] [02miraheze/ManageWiki] 07paladox 039dc1b3d - Update ManageWikiFormFactory.php [21:24:56] [02ManageWiki] 07paladox synchronize pull request 03#129: Fix "Call to a member function getFormSections() on bool" - 13https://git.io/JepOi [21:24:56] no, what should I set it to? [21:25:25] I don't see any info about this option on mediawiki.org [21:25:40] we have it set here https://github.com/miraheze/mw-config/blob/master/LocalSettings.php#L264 [21:25:41] [ mw-config/LocalSettings.php at master · miraheze/mw-config · GitHub ] - github.com [21:25:57] Skamp you can fork our repo if you want (changing stuff to match what your wiki is) [21:27:41] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/Jep3R [21:27:42] [02miraheze/ManageWiki] 07paladox 034d92656 - Update SpecialManageWikiDefaultPermissions.php [21:27:44] [02ManageWiki] 07paladox synchronize pull request 03#129: Fix "Call to a member function getFormSections() on bool" - 13https://git.io/JepOi [21:29:11] how should I get the dblist directory? Is it automatically generated? [21:29:35] oh, I think I get it [21:30:46] You create a cron which automatically generates it [21:31:02] (e.g we have it set to run every 1 minute) [21:31:09] [02ManageWiki] 07JohnFLewis reviewed pull request 03#129 commit - 13https://git.io/Jep3a [21:31:11] [02ManageWiki] 07JohnFLewis reviewed pull request 03#129 commit - 13https://git.io/Jep3V [21:31:12] [02ManageWiki] 07JohnFLewis reviewed pull request 03#129 commit - 13https://git.io/Jep3w [21:31:14] [02ManageWiki] 07JohnFLewis reviewed pull request 03#129 commit - 13https://git.io/Jep3r [21:31:21] It's used here https://github.com/miraheze/mw-config/blob/master/LocalSettings.php#L2972 [21:31:21] [ mw-config/LocalSettings.php at master · miraheze/mw-config · GitHub ] - github.com [21:34:40] [02ManageWiki] 07paladox synchronize pull request 03#129: Fix "Call to a member function getFormSections() on bool" - 13https://git.io/JepOi [21:34:42] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/Jep3M [21:34:43] [02miraheze/ManageWiki] 07paladox 0378c11af - Update ManageWikiFormFactory.php [21:34:53] ok, it generated some files, I set $wmgDatabaseList option. Nothing chaned [21:35:31] it looks like it's using all.dblist file. It created a tmp file [21:35:34] [02ManageWiki] 07paladox synchronize pull request 03#129: Fix "Call to a member function getFormSections() on bool" - 13https://git.io/JepOi [21:35:35] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/Jep3y [21:35:37] [02miraheze/ManageWiki] 07paladox 03de934bc - Update SpecialManageWiki.php [21:36:24] [02ManageWiki] 07paladox synchronize pull request 03#129: Fix "Call to a member function getFormSections() on bool" - 13https://git.io/JepOi [21:36:26] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/Jep37 [21:36:27] [02miraheze/ManageWiki] 07paladox 031e3374b - Update SpecialManageWikiDefaultPermissions.php [21:36:38] [02ManageWiki] 07paladox reviewed pull request 03#129 commit - 13https://git.io/Jep35 [21:36:44] [02ManageWiki] 07paladox reviewed pull request 03#129 commit - 13https://git.io/Jep3d [21:36:50] [02ManageWiki] 07paladox reviewed pull request 03#129 commit - 13https://git.io/Jep3F [21:37:14] [02ManageWiki] 07paladox reviewed pull request 03#129 commit - 13https://git.io/Jep3b [21:37:30] PROBLEM - wiki.8b8t.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:38:37] Skamp yeh, it'll create tmp then move it (it's to prevent a race condition) [21:39:34] RECOVERY - wiki.8b8t.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.8b8t.com' will expire on Fri 21 Feb 2020 05:25:26 AM GMT +0000. [21:39:50] [02ManageWiki] 07paladox closed pull request 03#129: Fix "Call to a member function getFormSections() on bool" - 13https://git.io/JepOi [21:39:52] [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/Jep3h [21:39:53] [02miraheze/ManageWiki] 07paladox 03eb9c302 - Fix "Call to a member function getFormSections() on bool" (#129) * Fix "Call to a member function getFormSections() on bool" Sometimes $formFactory->getForm can return a bool, so handle it correctly. * Update SpecialManageWiki.php * Update ManageWikiFormFactory.php * Update SpecialManageWikiDefaultPermissions.php * Update ManageWikiFormFactory.php * Update [21:39:53] SpecialManageWiki.php * Update SpecialManageWikiDefaultPermissions.php [21:40:27] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/Jepsv [21:40:28] [02miraheze/mediawiki] 07paladox 0309baaac - Update ManageWiki [21:42:34] [02ManageWiki] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vpSns [21:42:36] [02miraheze/ManageWiki] 07paladox deleted branch 03paladox-patch-2 [21:42:43] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 5 datacenters are down: 107.191.126.23/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [21:43:52] Skamp fix merged regarding your earlier issue (which would have helped you a bit more) [21:44:43] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [21:45:31] Skamp viewing Special:ManageWiki throws the error right? [21:45:51] yes. "That wiki does not exist. [21:46:16] on both the default and a wiki that I created [21:48:14] [02miraheze/CreateWiki] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JepsW [21:48:15] [02miraheze/CreateWiki] 07paladox 03cdf3535 - Switch to using User::newSystemUser for using 'MediaWiki default' [21:48:50] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/Jeps4 [21:48:51] [02miraheze/mediawiki] 07paladox 03b930377 - Update CreateWiki [21:50:46] miraheze/CreateWiki/master/cdf3535 - paladox The build was broken. https://travis-ci.com/miraheze/CreateWiki/builds/143053196 [21:51:03] seems it's failing because of https://github.com/miraheze/CreateWiki/blob/master/includes/RemoteWiki.php#L27 [21:51:03] [ CreateWiki/RemoteWiki.php at master · miraheze/CreateWiki · GitHub ] - github.com [21:51:57] Skamp use ; then select * from cw_wikis where wiki_dbname = ; [21:52:13] (mysql queries you shoud try directly) [21:53:24] it's in there [21:54:02] everything looks fine [21:54:51] Did you set https://github.com/miraheze/mw-config/blob/master/LocalSettings.php#L258 ? [21:54:52] [ mw-config/LocalSettings.php at master · miraheze/mw-config · GitHub ] - github.com [21:55:36] yes, and the $wgCreateWikiGlobalWiki [21:55:46] both pointing to the same database [21:56:11] hmm [21:56:12] maybe I should try starting from scratch? [21:56:22] JohnLewis maybe you can help ^? [21:56:42] What is the databse name of the wiki you are trying to access? [21:57:41] my main/meta wiki's database is 'rootwiki', the one I created is 'testwiki' [21:58:16] SELECT * FROM cw_wikis WHERE wiki_dbname = 'rootwiki'; does that return anything? [21:59:53] no, I only have 'testwiki' in there [22:00:16] paladox: there you go, you may carry on helping as I'm busy :) [22:00:24] :P [22:00:47] Skamp so if your trying to access Special:ManageWiki on rootwiki, it needs to have an entry in that table. [22:01:37] I understand that, but I also can't edit testwiki, even though it's in the table [22:02:52] should I create a rootwiki entry by myself by cloning the testwiki row and changing the values? [22:03:06] yeh [22:04:24] though [22:04:50] https://github.com/miraheze/ManageWiki/blob/1e3374b964194411f3b7948a5eb50f5f7f4b8a26/includes/specials/SpecialManageWiki.php#L37 then https://github.com/miraheze/ManageWiki/blob/1e3374b964194411f3b7948a5eb50f5f7f4b8a26/includes/specials/SpecialManageWiki.php#L99 show is hould be using 'testwiki' [22:04:51] [ ManageWiki/SpecialManageWiki.php at 1e3374b964194411f3b7948a5eb50f5f7f4b8a26 · miraheze/ManageWiki · GitHub ] - github.com [22:04:53] [ ManageWiki/SpecialManageWiki.php at 1e3374b964194411f3b7948a5eb50f5f7f4b8a26 · miraheze/ManageWiki · GitHub ] - github.com [22:11:58] Skamp in eval.php ( a mediawiki core maintenance script ) what does var_dump(wfGetDB( DB_MASTER, [], '' )->selectRow( 'cw_wikis', RemoteWiki::selectFields(), [ 'wiki_dbname' => 'testwiki' ], __METHOD__ )); [22:12:57] show? [22:15:17] object(stdClass)#159 (16) { [22:15:58] heh [22:16:07] object(stdClass)#159 (16) { [22:16:53] https://pastebin.com/3Dn0nSVA [22:16:54] [ object(stdClass)#159 (16) { ["wiki_dbname"]=> string(8) "testwiki" ["wi - Pastebin.com ] - pastebin.com [22:17:13] Thanks [22:17:23] Oh! [22:17:26] * paladox dumb [22:17:35] you can access Special:ManageWiki/core/testwiki [22:17:41] but Special:ManageWiki/core fails [22:17:55] as said, you'll need to create an entry for rootwiki :) [22:18:02] Since that'll use the currents wiki db [22:18:11] *name [22:18:15] Ok, now I have a list of settings and extensions i can edit. But how can I actually enable/disable an extension? [22:18:26] I created the 'rootwiki' row [22:19:15] Skamp you can do that with https://github.com/miraheze/mw-config/blob/master/ManageWikiExtensions.php [22:19:15] [ mw-config/ManageWikiExtensions.php at master · miraheze/mw-config · GitHub ] - github.com [22:19:16] and [22:19:22] https://github.com/miraheze/mw-config/blob/master/ManageWikiSettings.php [22:19:23] [ mw-config/ManageWikiSettings.php at master · miraheze/mw-config · GitHub ] - github.com [22:19:39] that'll set a config, that's set to false in LocalSettings [22:19:51] which then triggers loading the extension in LocalExtension.php [22:20:14] no, I did that, I have a list of extensions I can enable [22:20:21] oh [22:20:35] but how does it actually enable the extension? [22:20:42] you click the tick box [22:20:46] then click "submit" [22:20:54] remember to set the config in LS. [22:20:59] for example: [22:21:09] wmgUse3D [22:21:21] is set to false in LocalSettings.php [22:21:30] https://github.com/miraheze/mw-config/blob/master/LocalSettings.php#L519 [22:21:30] [ mw-config/LocalSettings.php at master · miraheze/mw-config · GitHub ] - github.com [22:21:53] which when set to true (by ManageWikiExtensions), it'll load the extension from LocalExtension [22:22:06] https://github.com/miraheze/mw-config/blob/master/LocalExtensions.php#L4 [22:22:06] [ mw-config/LocalExtensions.php at master · miraheze/mw-config · GitHub ] - github.com [22:22:07] no no no, I understand that. Im talking about how the extension enables it. It's like a programatic wfLoadExtension? [22:22:09] oooh [22:22:12] I get it now [22:33:59] ok, I'll try to get things working on my own now. Thank you very much for help, I really appreciate it. And good luck on the project you are running [22:39:26] [02miraheze/MatomoAnalytics] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JepGn [22:39:27] [02miraheze/MatomoAnalytics] 07paladox 039392a88 - Support disabling cookies set by matomo/piwik [22:39:29] [02MatomoAnalytics] 07paladox created branch 03paladox-patch-1 - 13https://git.io/fN4LT [22:39:30] [02MatomoAnalytics] 07paladox opened pull request 03#14: Support disabling cookies set by matomo/piwik - 13https://git.io/JepGc [22:40:20] [02miraheze/MatomoAnalytics] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JepGC [22:40:21] [02miraheze/MatomoAnalytics] 07paladox 03748793c - Update extension.json [22:40:23] [02MatomoAnalytics] 07paladox synchronize pull request 03#14: Support disabling cookies set by matomo/piwik - 13https://git.io/JepGc [22:41:14] [02miraheze/MatomoAnalytics] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JepGW [22:41:16] [02miraheze/MatomoAnalytics] 07paladox 03d5b7200 - Update CHANGELOG [22:41:17] [02MatomoAnalytics] 07paladox synchronize pull request 03#14: Support disabling cookies set by matomo/piwik - 13https://git.io/JepGc [22:43:22] miraheze/MatomoAnalytics/paladox-patch-1/d5b7200 - paladox The build was broken. https://travis-ci.org/miraheze/MatomoAnalytics/builds/632477210 [22:43:51] [02MatomoAnalytics] 07paladox edited pull request 03#14: Support disabling cookies set by Matomo/Piwik - 13https://git.io/JepGc [22:44:14] [02MatomoAnalytics] 07paladox closed pull request 03#14: Support disabling cookies set by Matomo/Piwik - 13https://git.io/JepGc [22:44:16] [02miraheze/MatomoAnalytics] 07paladox pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/JepGR [22:44:17] [02miraheze/MatomoAnalytics] 07paladox 031fc2bf4 - Support disabling cookies set by matomo/piwik (#14) * Support disabling cookies set by matomo/piwik * Update extension.json * Update CHANGELOG [22:44:19] [02miraheze/MatomoAnalytics] 07paladox deleted branch 03paladox-patch-1 [22:44:20] [02MatomoAnalytics] 07paladox deleted branch 03paladox-patch-1 - 13https://git.io/fN4LT [22:45:05] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JepGE [22:45:07] [02miraheze/mw-config] 07paladox 03ca03acc - Set wgMatomoAnalyticsDisableCookie to true [22:45:38] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JepGz [22:45:39] [02miraheze/mediawiki] 07paladox 03629595c - Update MatomoAnalytics [22:46:26] miraheze/MatomoAnalytics/master/1fc2bf4 - paladox The build was broken. https://travis-ci.org/miraheze/MatomoAnalytics/builds/632478128 [22:48:09] [02miraheze/MatomoAnalytics] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JepGV [22:48:11] [02miraheze/MatomoAnalytics] 07paladox 0315c7c9c - Fix to make it a noun in description for MatomoAnalyticsDisableCookie [22:48:42] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_34 [+0/-0/±1] 13https://git.io/JepGw [22:48:43] [02miraheze/mediawiki] 07paladox 0378d7f08 - Update MatomoAnalytics [23:03:35] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 1 datacenter is down: 2a00:d880:5:8ea::ebc7/cpweb [23:05:35] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online