[14:25:09] If I'm creating a user script using ES6, mediawiki will translate it with a babel to ES5? [17:40:16] not sure if i report this here or elsewhere but fr.wikiquote.org is broken [17:41:59] https://fr.wikiquote.org/wiki/Wikiquote:Accueil [17:42:00] WFM [17:42:03] Chrissymad: What's broken about it? [17:43:08] it's french. [17:43:12] evidently. [17:43:53] Reedy: i and others have tried to access it (the main page loads usually) and then it blanks and goes into an endless cycle of loading. RC doesn't even load (I tried logged out, incognito, on my phone etc..) SQL had the same problem i believe [17:44:26] Hmm. I see that too [17:44:49] it's strange - it starts to load then goes blank and then just acts like it's loading forever [17:45:06] IT seems to be VE related [17:45:21] [17:45:43] Deskana: ^ VE is your problem these days, right? :P [17:46:20] i thought spambots broke it [17:47:30] Any idea when it started? [17:48:51] James_F: ^ Halp [17:49:21] Ask someone not running Metrics please. [17:49:27] Suggestions who? [17:49:34] I've no idea who cares about VE these days [17:50:24] if you're asking me, i just got a hit on a meta filter for a spambot and went to check [17:51:02] What was the filter hit? [17:51:45] 13:48, 26 April 2018: User: (fr.wikiquote.org) triggered filter 104, performing the action "edit" on Mystic Cove Non Secular Holistic Way Of Life Centre Craft Store. Actions taken: Warn; Filter description: Unregistered spam containing double linebreaks (details | examine) [17:52:17] https://meta.wikimedia.org/wiki/Special:AbuseLog/393415 [17:53:02] Seems unrelated [17:53:13] Wiki looks pretty quiet atm though [17:54:26] i was kidding about spambots breaking it fwiw [17:57:58] Reedy works when using lang en [17:58:03] (changed it from fr to en) [17:58:07] Try loading after [17:58:13] oh [17:58:25] only when i do edit, which was not working before. [17:58:34] * Chrissymad can't even get to that point [18:21:36] Chrissymad: Filed as https://phabricator.wikimedia.org/T193191 [18:21:44] ty [18:25:17] Chrissymad: Thanks for finding it! [18:26:42] James_F: you can thank the spambot [18:26:43] :P [18:26:57] Chrissymad: If it's all the sameā€¦ ;-) [18:28:54] * Chrissymad is secretly the spambot [22:05:16] is there any way to get the api to return logs of only certain types, without requesting each type one by one? [22:06:11] for example, if you want the move log, protection log, and deletion log, without all the other logs, in one api request? [22:06:17] Yes [22:06:19] https://en.wikipedia.org/w/api.php?action=help&modules=query%2Blogevents [22:06:37] letype=protect|move|delete [22:07:07] Reedy: that gives an error message [22:07:22] code: "multival_letype" [22:07:35] Oh [22:07:37] Then no "{ [22:07:39] :P [22:07:41] Make 3 requests [22:07:49] okay then [22:07:50] thanks [22:33:52] has anyone filed a bug in the past few days over the broken PDF thumbs? [22:33:57] if not I will [22:37:36] Broken meaning... [22:41:40] Magog_the_Ogre: yes I'm looking into that problem right now actually :) [22:41:56] it may be an issue with the pdfinfo command being updated to an incompatible version [22:42:07] fix is in the works but i'm trying to validate that it's that problem in fact [22:42:29] https://phabricator.wikimedia.org/T193200 <- https://phabricator.wikimedia.org/T117839 [22:43:26] thanks brion. If you want to see a page where a bunch are broken, check out https://commons.wikimedia.org/wiki/User:OgreBot/Notable_uploads/2018_April_25 [22:43:47] tx [22:44:47] brion: Some security updates were installed a couple of days ago [22:44:49] 06:41 moritzm: installing poppler security updates [22:45:26] suspicious [22:45:44] i'll ping him on the task [22:47:56] It's quite possible other updates have sneaked in, or package bumps [22:49:09] yeah. most likely we had an old package held over in wmf that's been replaced with a current package [22:49:23] i'm just vague on how to queyr info and histor of our apt repo :D [22:50:33] ii libpoppler46:amd64 0.26.5-2+deb8u4 amd64 PDF rendering library [22:50:33] ii poppler-data 0.4.7-1 all encoding data for the poppler PDF rendering library [22:50:33] ii poppler-utils 0.26.5-2+deb8u4 amd64 PDF utilities (based on Poppler) [22:50:36] is the current.. [22:50:50] hmmm, interesting [22:51:45] then... [22:51:45] Commandline: apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install poppler-utils=0.26.5-2+deb8u4 libpoppler46=0.26.5-2+deb8u4 [22:51:45] Upgrade: libpoppler46:amd64 (0.26.5-2+deb8u3, 0.26.5-2+deb8u4), poppler-utils:amd64 (0.26.5-2+deb8u3, 0.26.5-2+deb8u4) [22:51:54] that's on a debian 8 host [22:52:00] looks a very minor bump at least [22:53:49] and yet my vagrant VM has 0.48.0 [22:53:59] ah that's 9 right [22:54:15] do we have debian 9 hosts running mw? [22:55:19] log says.... yes we do :D [22:55:25] do they have 0.26.5 or 0.48.0? [22:55:51] any idea which might be? :P [22:56:22] 11:44 moritzm: reimaging mw1241, mw1242, mw1243 (app servers) to stretch [22:56:22] 10:58 moritzm: reimaging mw1224, mw1225, mw1226 (API servers) to stretch [22:56:54] ii libpoppler64:amd64 0.48.0-2+deb9u2 amd64 PDF rendering library [22:56:54] ii poppler-data 0.4.7-8 all encoding data for the poppler PDF rendering library [22:56:54] ii poppler-utils 0.48.0-2+deb9u2 amd64 PDF utilities (based on Poppler) [22:56:56] woo, mixed fleet [22:57:36] so yeah, seems quite possible some requests are hitting them [22:57:41] yeah [22:57:46] ok so that solves the mystery i think :D [22:57:54] thanks for the help checking hosts Reedy ! [22:58:12] heh, np [22:58:29] Your patch probably wants backporting to 1.27/1.29/1.30/1.31 :) [22:59:44] yep :( [23:00:00] original bug was reported like two and a half years ago [23:00:07] it just never hit us cause we didn't update ;) [23:00:16] I suspect it should be a trivial backport [23:01:27] yeah