[12:00:24] ey, anyone mind deleting a page on beta real quick? [12:01:36] ok [12:01:46] any particular page or should I just pick one? [12:02:01] https://deployment.wikimedia.beta.wmflabs.org/wiki/User:TerraCodes [12:02:39] poof [12:03:27] thanks [14:00:24] Technical Advice IRC meeting starting in 60 minutes in channel #wikimedia-tech, hosts: @alaa_wmde & @nuria - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting [14:50:22] Technical Advice IRC meeting starting in 10 minutes in channel #wikimedia-tech, hosts: @alaa_wmde & @nuria - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting [15:02:05] *ding* [15:02:09] hey! [15:02:18] *dong* [15:02:29] ...the witch is dead? [15:03:09] lol [15:03:29] o/ [15:03:30] can be bg music why not [15:03:44] \o tgr [15:08:07] while I wait for someone to show up with real questions, here's one: does the rewrite of parsoid in php mean that parsoid will be a mw extension [15:08:20] or will it remain a service somehow? what's the architecture going to be? [15:09:24] not quite an extension but yes, it will be invoked in-process [15:09:34] not immediately though [15:10:23] does 'not quite an extension' mean it will move into core? [15:10:32] how was it written previously? [15:10:57] is it this one https://github.com/wikimedia/parsoid? [15:11:07] mostly a composer library, probably [15:11:22] nodejs [15:11:50] previously it was a standalone node.js service with RESTBase caching, yeah [15:13:32] yes that's the repo [15:14:02] I understand the back end won't change (at least for now), just asking about the service piece [15:14:03] thanks [15:16:36] first switch is to an 1:1 port to PHP, which can be accessed via the MediaWiki REST API [15:16:49] so it's a drop-in replacement for the current service [15:17:28] longer term it will replace the PHP parser, which means being called in-process and in real time [15:18:07] oh wow, replacing the existing parser, that's huge [15:19:20] interesting.. I learned two new things already in this session :D [15:19:22] is there a draft roadmap around for folks who want to follow along? [15:21:46] this looks like a starting point https://www.mediawiki.org/wiki/Parsing/Notes/Moving_Parsoid_Into_Core/Porting [15:23:31] great find, thanks! [15:24:15] theres lso this board now https://phabricator.wikimedia.org/project/view/3594/ [15:24:51] from https://www.mediawiki.org/wiki/Parsing/Notes/Moving_Parsoid_Into_Core/Porting#Make_use_of_types, it looks like Parsoid-in-MW definitely won’t happen before the PHP7.2 migration is done [15:25:08] though I guess PHP-Parsoid-as-service isn’t bound by that [15:25:15] it shouldn't be [15:25:26] and php7.2 migration is going quite well [15:25:52] * alaa_wmde amused [15:26:22] or rather happy to hear that :) [15:26:35] yay [15:26:42] https://phabricator.wikimedia.org/T219150 for progress [15:27:02] (I gotta run now, hope many other questions are asked and answered! will do the backread later) [15:31:42] oh, 10% already went live? nice [15:32:34] While installing an extension, I get 'extension.json does not exist!' on creating a symbolic link but works fine if I download directly into the extensions/ dir. Why is this happening? [15:37:12] * alaa_wmde checking [15:39:26] probably web server security settings? [15:44:27] I can reproduce it simply by symlinking somewhere outside the extensions follder [15:46:02] symlinking to another folder within extensions folder itself works fine .. so it is more likely now to be related to server configs as tgr [15:46:13] ... suggested [15:47:19] MediaWiki does a plain file_exists [15:49:27] you might have Apache with FollowSymlinks disabled, you might have open_basedir in PHP config, you migh be using some extra hardening like SELinux, etc [15:51:45] pavithraes: are u using apache or nginx? how does the configuration look like? [16:05:33] so yeah file_exists is used internally which means symbolic links for extension folders cannot be used for now [16:08:15] alaa_wmde: [16:08:50] alaa_wmde: I'm using Apache. [16:10:40] alaa_wmde: Makes sense. I'll look into it. [16:13:46] pavithraes: I tried even with mount binding on filesystem but that caused same issue .. I believe we'll need probably to change media wiki to account for symlinks in order to make this work [16:22:58] FollowSymLinks is enabled [16:34:10] https://lists.wikimedia.org/pipermail/wikitech-l/2019-May/092099.html - Finally got IRCCloud working [16:34:43] What's on Group 1? [16:34:56] If you don't know - train reverted [16:36:03] RhinosF1: Roughly, all wikis that aren't Wikipedias and aren't a test wiki. [16:37:54] plus a handful of Wikipedias, apparently: https://noc.wikimedia.org/conf/highlight.php?file=dblists/group1-wikipedia.dblist [16:40:47] Yup, "roughly". :-) [16:41:28] E.g. group0 includes MediaWiki.org, locked wikis, officewiki, and a couple of others. [18:18:52] https://wikitech.wikimedia.org/wiki/Deployments/One_week list of which wikis are in which group, RhinosF1 [18:20:44] apergos, Thanks, That's the nicest displayed of the few I've seen [18:20:51] yw :-) [18:22:26] apergos, Is this best task to track deployment on? https://phabricator.wikimedia.org/T224116 [18:22:44] RhinosF1: I'm deploying now. [18:23:40] James_F, Ah, Cool. Good luck! Also why didn't stashbot give the task title for that. [18:24:06] No recent comments from stashbot in this channel; maybe it's broken? [18:24:37] https://tools.wmflabs.org/versions/ this is where you can keep track of what's actually running [18:26:54] Ah that will have to be the next task, Fixing stashbot, A good day for the Devs. [18:28:07] RhinosF1 it's because the bot only likes T224116 not https://phabricator.wikimedia.org/T224116 [18:28:08] T224116: operand type was used: expects array(s) or collection(s) in /srv/mediawiki/wmf-config/flaggedrevs.php on line 182 - https://phabricator.wikimedia.org/T224116 [18:28:18] Oh, right. [18:31:03] Paladox, or maybe restarting my brain is the next task [18:31:09] heh [18:32:01] Paladox, :) - try !RhinosF1 update [18:32:17] Then !RhinosF1 restarting [18:32:23] *restart [19:12:33] thedj: Is this still something we want to do? https://phabricator.wikimedia.org/T132946 [19:15:40] Krinkle: Is there a way TMH can splice the "transcodes" object into the imageinfo response? [20:10:34] James_F: maybe, not sure if that is extendable. [20:11:43] I think the WBMI people were looking at splicing in their captions into files. [20:11:47] * James_F hunts for tasks. [20:12:06] Oh, right, it's marked as blocked by T132947. [20:12:12] T132947: Make it possible for extensions to add additional info to the fileinfo/imageinfo response. - https://phabricator.wikimedia.org/T132947