[00:00:32] Or you force a run on jenkins :) [00:01:08] still running [00:01:49] I just eval.php-d $wgEnableBotPasswords and it was set [00:02:25] git log? [00:03:20] ofc I did that on deployment-bastion, I suppose that doesn't count for much [00:03:57] beta-scap-eqiad is still running [00:04:03] so it might not be out yet [00:04:22] it's still building the new l10n cache files last time I looked [00:04:39] ok, thanks [00:04:45] that's mostly what deployment-bastion does these days :/ [00:04:59] maybe when we get a new version of php... [00:05:03] s/php/hhvm/ [00:07:58] good to see sessions are still screwed on wikitech :D [00:10:13] Build has been executing for 29 min on deployment-bastion.eqiad [00:10:20] I guess that's not unexpected, with a lot of new messages etc [00:10:25] l10nupdate is all about file system stat calls [00:10:54] when we get a big batch of data from translatewiki it takes a long time to digest on the beta cluster [00:11:03] deployment-bastion is not beefy [00:11:55] I was meaning changing the localisation cache back again etc [00:12:31] ah. it's faster at runtime but building it is just as slow [00:12:45] actually slower the way we did it I think [00:13:01] I think the code we have turns the cdb into php [00:13:07] so another step [00:13:11] lol [00:16:19] bd808: anomie: merged all the things [00:16:28] sweet! [00:16:34] the bot password migration did not work: http://en.wikipedia.beta.wmflabs.org/wiki/Special:BotPasswords [00:16:42] one step closer to world domination [00:16:45] maybe that's also a lag issue? [00:17:14] need to create the table in prod [00:17:29] (I should probably get into the habit of doing that before merge) [00:17:38] are we putting that in metawiki? [00:18:04] not sure... [00:18:33] I guess meta would be the right place. That's where we do oauth now right? [00:18:39] yes [00:19:28] does that mean we need to be able to turn off the special page on other wikis too? [00:19:28] Creating empty tables is cheap at least :_ [00:19:33] * :) [00:19:35] apart from the bot password email we should probably send a mail about sessionmanager and pinging us in case of weirdness [00:19:48] should I do that? [00:19:57] (after I tested things a bit more) [00:20:08] yeah, anomie wanted me to remind hime to do that. You certainly can if you know what to say [00:20:13] the special pages should work fine [00:20:58] I don't think the current code even allows disabling it without fully disabling bot passwords on that wiki [00:21:15] but usability-wise, it makes much more sense if it works locally [00:21:38] oauth grant management does that as well IIRC, only the admin stuff is centralized [00:22:58] I wonder what happens if someone uses update.php on a wikifarm though [00:23:10] or are you generally not supposed to do that? [00:26:08] tgr: for my wikifarms, I usually apply the sql patches manually and then run the equivalent of foreachwiki update.php --quick [00:28:01] the bot_passwords table is created on all wikis, even if a central wiki is configured [00:28:16] that works differently with oauth, but meh [00:28:52] I wonder whether we should send an email when a bot password is set [00:29:15] I don't think anyone will care if extra db tables are created but not used [00:32:33] where would the error log from beta update.php go? [00:35:18] it should be in the console logs on jenkins [00:36:53] Reedy: that's https://integration.wikimedia.org/ci/job/beta-update-databases-eqiad/ ? [00:37:12] Yeah [00:37:13] https://integration.wikimedia.org/ci/job/beta-update-databases-eqiad/5753/console [00:37:30] 23:21:50 Warning: include(/mnt/srv/mediawiki-staging/php-master/extensions/LandingCheckLandingCheck.alias.php): failed to open stream: No such file or directory in /mnt/srv/mediawiki-staging/php-master/includes/cache/LocalisationCache.php on line 527 [00:37:40] 23:21:50 Warning: include(/mnt/srv/mediawiki-staging/php-master/extensions/SubpageSortkey/SubpageSortkey.alias.php): failed to open stream: No such file or directory in /mnt/srv/mediawiki-staging/php-master/includes/cache/LocalisationCache.php on line 527 [00:37:55] * Reedy looks [00:38:31] nothing relevant as far as I can see [00:38:35] it's a core migration [00:39:01] It might be the build before/after [00:39:25] I'll just wait a bit then, it apparently runs once an hour [20:24:51] tgr: are you an oauth approver? Sage is looking for this to be approved -- https://meta.wikimedia.org/wiki/Special:OAuthListConsumers/view/f9c73af2e3a3145ea0bda50407d79c38 [20:27:13] Looks like Reedy, anomie, robla, AaronSchulz are the people here I should bug ^ [20:27:28] not me right now [20:27:30] bd808: not as such but I'm in the global dev group [20:28:01] I can do it [20:28:25] it's auth only so shouldn't be too hard to evaluate [20:30:27] There's 3 other consumers with the same name [20:30:31] ish [20:30:35] Wikipedia Playlist [1.0] [20:30:42] WikiPlaylist [1.0] [20:30:48] Wikipedia Playlist (Staging) [1.0] [20:30:53] Wikipedia Playlist (Staging) [1.1] [20:31:45] Be nice to clear some of them up [20:32:03] bd808: approved [20:32:11] <3 Reedy [20:32:18] Do you have a contact there? [20:32:44] ah, I'll ask in there [20:42:53] [20:37:31] Anyway to use VisualEditor without Parsoid? [20:42:53] [20:37:39] I dont have access to my server to install it [20:42:53] [20:37:44] bb8r2d2: No, sorry. [20:42:56] James_F is the worst. [20:43:09] Yes I am. [20:52:23] * bd808 appreciates that James_F answers these questions :) [20:52:44] James_F: is there a technical blocker to someone running parsoid as a SaaS or is that just a question of someone doing it? [20:53:06] as I understand it communicates with the wikis via public APIs and has no private data access of its own [20:57:58] tgr: Well, nowadays we're encouraging people to use RESTbase rather than Parsoid directly, and RB will (but doesn't yet) do private data access. [20:58:25] tgr: But yeah, if I had the time I'd get us to run MediaWiki.com with a hosted RB/Parsoid instance for people. [20:58:54] (If only.) [20:59:19] James_F: but theoretically, anyone could do that, right? [20:59:38] without having to do serious parsoid development I mean [21:00:10] sounds like the thing for which it should not be hard to find interested non-WMF developers [21:15:30] Hi does anyone know how to load js files from other websites through resouceloader instead of using Html::linkedScript [21:24:07] paladox: there was a wikitech-l email thread about that a few days ago [21:24:41] tgr: Oh. do you know if it was answered. [21:24:45] please. [21:24:45] you need to use mw.loader but there were some code examples in that thread IIRC [21:25:02] tgr: Do you know what the name of that email was called. [21:25:15] I could look through since i am signed up to that i think. [21:25:20] something about resourceloader [21:25:39] it was just 2-3 days ago, should be easy to find [21:26:34] in general though, #mediawiki or #wikimedia-dev is probably a better channel to ask [22:02:03] tgr: RESTBase does have private wiki support these days, but we have not enabled it yet in production [22:02:58] tgr: Yes. [22:03:13] bd808: If I didn't answer the questions people would be stranded, which isn't cool. But thank you. :-) [22:03:14] gwicke: Oh, interesting. Is it going through security review? I'd really love to switch our last few wikis over. [22:20:30] csteipp, dapatrick: addshore and I are going to have an extension for https://phabricator.wikimedia.org/T43327 that will be ready for a security review in late Jan/early Feb [22:20:41] :) [22:23:18] legoktm: Cool, can you make a #security-reviews task for that? [22:23:56] legoktm: Also, I was looking at possibly scheduling Newsletter this quarter. preference on priority? [22:24:35] csteipp: will do :) I'm actually not involved with Newsletter... I think addshore is though :P [22:33:40] legoktm: I cracked a big grin when I saw the page you used for the mockup in T43327. Just short of an actual LOL [22:34:23] haha :))) [22:35:00] legoktm: csteipp vaguely (Newsletter that is) [22:35:44] bd808: legoktm Taylor swift? [22:36:02] yup [22:36:05] http://tay.today/ [22:38:20] James_F|Away, csteipp: we discussed the approach at the time, but it hasn't been thoroughly security-reviewed [22:38:42] the code is merged & deployed, but we have not enabled RB for private wikis yet [22:44:39] legoktm: We have a page that documents some information we like to have when doing reviews. [22:44:40] I [22:44:43] I [22:44:53] I'm looking for that wiki page right now. [22:45:47] dapatrick: https://www.mediawiki.org/wiki/Wikimedia_Security_Team/Security_reviews#Requesting_a_review ? [22:46:00] Ah, yep. [22:46:51] I saw in the scrum of scrum notes to schedule reviews so :) [22:47:33] legoktm: There a link on that page that populates a phab ticket with some fields to fill out. [22:47:41] Hopefully that makes it a little easier. [23:03:35] legoktm: still my phone background... [23:03:51] I need to set that up :D [23:13:40] task is https://phabricator.wikimedia.org/T123592?workflow=create