[01:54:05] phab down? [01:57:43] Shizhao: yes, it's being upgraded right now [02:29:22] Does the same "botpassword" work on more than one wiki? [02:39:08] kolbert: yes, I think it should [02:39:23] Okay :) thank you [12:12:57] The "welcome to Wikipedia" splashscreen popup is so slow to load that quite often I manage to edit and save before it captures the window [13:09:07] [[Tech]]; Coolak; /* Wiki editor issues on Firefox 57 */ new section; https://meta.wikimedia.org/w/index.php?diff=17429950&oldid=17429359&rcid=10881977 [13:27:34] [[Tech]]; Coolak; /* Wiki editor issues on Firefox 57 */; https://meta.wikimedia.org/w/index.php?diff=17429988&oldid=17429950&rcid=10882031 [14:10:25] bblack: Shouldn't / be Always-Encode [14:13:04] Also ~ (annoyingly) is always encode in MW [14:13:28] Dispenser: in both cases, not for MediaWiki, no. It's part of the wfUrlencode set that's always-decode. [14:14:14] Dispenser: https://github.com/wikimedia/mediawiki/blob/f489fe483d1b63ef0592b5b0cc3ed744a6d1a4c6/includes/GlobalFunctions.php#L410 [14:18:26] Ok, I see ~ been change. And : \ / is disallowed in file names https://www.mediawiki.org/wiki/Manual:$wgIllegalFileChars [14:19:02] https://en.wikipedia.org/w/index.php?title=/&redirect=no [14:19:06] https://en.wikipedia.org/w/index.php?title=~&redirect=no [14:19:22] (both of those "work", although they're not actual article names, just title redirects) [14:21:21] technically though, while the Title/File rules are informative here, they're not really the basis for the normalization rules, which is a bit further out in scope. [14:21:50] Outside WMF ; very rarely is some kind of delimiter [14:22:06] e.g. if /wiki/File:foo doesn't allow "foo" to contain :/\, that doesn't mean we have to normalize them any different. We can apply some consistent normalization to those and they'll turn into errors or whatever. [14:23:33] the goal here is to have a simple rule that applies to all URLs we pass down to MediaWiki (in the WMF), that results in one canonical encoding of any URL. [14:23:56] (well, URL path, I should say. the query part isn't included here) [14:26:17] https://tools.ietf.org/html/rfc2396.html [14:28:39] You can do an href="g;x=1/./y" and its suppose to normalize it to http://a/b/c/g;x=1/y [14:29:47] Hi folks, is this the right place to ask about Quarry? :) [14:43:57] yeah I've read the RFC. By the RFC's general-case rules, there is no way for a generic intermediate cache to apply complete normalization sanely. [14:44:42] the intermediate cache can basically un-encoded the unreserved set safely, but can't un-encode or encode anything else in transit. [14:45:12] what we're doing here is MW-specific + WMF-specific. [14:45:59] given we know the target is our own MediaWiki appservers, is applying this strict encoding-normalization to the path part of the URL sane? (as in, it won't break any requests that wouldn't already be broken in their original form) [14:46:23] (or cause some horrible redirect loop because Varnish is translating /X -> /Y, and MW is saying /Y is a redirect to /X) [14:49:26] the goal of the strict normalization is to ensure there's no aliasing in Varnish. [14:49:46] (that there aren't two different URL-encodings /X and /Y which map to the same content in MW but cache separately in Varnish) [14:49:48] Jhs: maybe #wikimedia-cloud but try? [17:01:54] [[Tech]]; Quiddity; /* Renan Feitosa */ unsigned, late reply; https://meta.wikimedia.org/w/index.php?diff=17430698&oldid=17429988&rcid=10883167 [17:32:20] for people who might be reporting various databases being locked [17:32:26] we are aware and it's being investigated [17:33:03] if you want to follow along (quietly please), you can join the #wikimedia-operations channel [17:37:27] Hi, I cannot edit, it seems like de.wikipedia is in read-only mode [17:38:20] (07:32:20 μμ) apergos: for people who might be reporting various databases being locked [17:38:20] (07:32:26 μμ) apergos: we are aware and it's being investigated [17:38:20] (07:33:03 μμ) apergos: if you want to follow along (quietly please), you can join the #wikimedia-operations channel [17:49:38] can someone change the topic then? [17:50:04] pretty sure I don't have ops in these channels [17:50:21] but give it about 5 minutes and I think we'll be in better shape [17:50:58] failover to new master for s5 (dewiki, wikidatawiki) now being deployed [17:56:46] mark, TimStarling: please chang channel topic to notify about failures [17:57:05] failover should be complete, need to re-enable a health monitoring piece on the new box [17:57:09] ma rk is on vacation [17:57:19] apergos: ok, then it made sense to ask someone else too [17:57:48] tim starling is probably not awake (wrong tz) [17:57:52] it was a nice thought [17:58:25] a moment then [17:59:26] robh: can you change channel topic to notify about failures please? [18:00:40] thanks [18:00:43] welcome =] [18:01:06] I wonder if it might be better to add a banner to the main page of some of the websites too [18:01:11] puppet change for fixing up the health monitor is going out now [18:01:22] that might reach more people than this topic [18:01:39] master going to be set as read write shortly, enabling edits again [18:05:51] b_jonas: there is also https://twitter.com/wikimediatech for more frequent updates, when admins !log stuff in a channel [18:09:24] there is a schema change rollback that must be applied to some replicas, this is being worked on now [18:10:18] retraction: it was being considered, apparently rejected as a possibility [18:16:33] because the schema on the master and (most of?) the slaves is different, there is a discussion about how to work around this and still provide service [18:18:28] <_joe_> we *are* going to do the revert, most probably. We are operating in degraded mode as far as dewiki and wikidata are concerned [18:32:34] no updates here because people are talking through the alternatives very carefully still [18:36:35] <_joe_> so we're back to read-only while we decide the best course of action; it's frankly better to be read-only than to risk data corruption IMHO [18:41:58] [[Tech]]; Trustable; /* Database read-only */ new section; https://meta.wikimedia.org/w/index.php?diff=17431077&oldid=17430698&rcid=10883662 [18:44:12] [[Tech]]; Sjoerddebruin; /* Database read-only */; https://meta.wikimedia.org/w/index.php?diff=17431085&oldid=17431077&rcid=10883671 [18:44:58] [[Tech]]; Sjoerddebruin; /* Database read-only */ link; https://meta.wikimedia.org/w/index.php?diff=17431090&oldid=17431085&rcid=10883680 [18:47:30] [[Tech]]; Mutante; [none]; https://meta.wikimedia.org/w/index.php?diff=17431098&oldid=17431090&rcid=10883693 [18:48:16] [[Tech]]; Mutante; /* Database read-only */; https://meta.wikimedia.org/w/index.php?diff=17431099&oldid=17431098&rcid=10883694 [18:54:49] [[Tech]]; Mutante; /* Database read-only */ re-adding comment i did not mean to remove, sorry; https://meta.wikimedia.org/w/index.php?diff=17431129&oldid=17431099&rcid=10883725 [18:57:04] the schema change is to be reverted on the replicas that were updated, so they can be brought back into service. this will take some hours at least. some services for dewiki and wikidatawiki may be degraded during this time [18:58:56] I probably won't update here again tonight, if there are any developments people can check the logs of the #wikimedia-operations channel, or join the channel and watch live, or check changes that are logged bia our twitter feed [18:59:18] https://twitter.com/wikimediatech [18:59:25] *via [19:38:59] hi there [19:39:33] Is there a sysadmin who can check the status of 2 global renames, it seems they are stuck [19:40:51] I wil ask you to rreport those in #wikimedia-operations if you don't mind [19:41:15] ok no problem [19:41:23] thank you [19:41:23] I wasn't sure where I should report it [19:41:26] thank you too [19:41:38] this is a fine place but I think people there need to hear about it [19:45:39] a phab ticket is probably best for those [19:46:29] I can't find any example of such ticket on phab [19:46:42] (to know how to present it, or which queue to select) [19:49:29] sorry, I thought someone might pick up in the other channel but meh [19:50:53] Linedwell: you can just put the same text you would put on IRC [19:51:02] people can handle the rest [19:51:07] ok [19:51:11] I'll do that [19:51:16] thank you mutante [19:51:45] you're welcome. just treat it like an email. fill out subject and "body" and somebody will add some tags [19:51:47] https://phabricator.wikimedia.org/T31757 here's a tracking task in case it's worth anything [19:51:52] seems to even get used for subtasks [20:38:59] good news: the global renames fixed themselves :) [20:42:16] excellent! [20:46:22] yes [20:46:38] I suspect some elves to have fixed it [22:45:45] [[Tech]]; 204.76.0.33; [none]; https://meta.wikimedia.org/w/index.php?diff=17431706&oldid=17431129&rcid=10884636 [22:46:10] [[Tech]]; 204.76.0.33; [none]; https://meta.wikimedia.org/w/index.php?diff=17431708&oldid=17431706&rcid=10884638 [22:46:22] [[Tech]]; Tegel; Reverted changes by [[Special:Contributions/204.76.0.33|204.76.0.33]] ([[User talk:204.76.0.33|talk]]) to last version by Mutante; https://meta.wikimedia.org/w/index.php?diff=17431710&oldid=17431708&rcid=10884640