[12:01:45] duesen: ping! [12:43:39] ping [12:43:46] duesen? [13:02:58] Amir1: hey [13:05:45] duesen: what's up? [13:05:52] Do you want to have it now [13:06:05] (or any other time) [13:06:59] Amir1: oh hey, sorry. Got lost in family stuff, lost track of time. [13:07:13] all good ^^ [13:07:20] I'll be with you in a couple of minutes, let me grab something to eat :) [13:07:29] Sure [13:11:48] Amir1: hm, first google logged me out, now puleaudio crashed... just a sec ;) [13:47:12] * Majavah literally has more than a vertical monitor full of Phan errors [14:59:08] Amir1: I'm looking at your patch that makes the installer fail safely when upgrading from before 1.26. Are you planning to make another patch that makes it so it fails from updating from anything older than 1.31? [14:59:29] Per the RFC, that'S the limit now, right? [15:08:18] duesen: yeah but I want to do it gradually [15:08:41] mostly because finding an implicit marker is hard [15:13:08] Amir1: ok. i commented. [15:15:22] duesen: I changed the wording a bit. Does that sound good to you? [15:15:46] I can manually test it by creating an empty hitcounter table. Is that enough? [15:16:14] Yes, looks good. [15:16:23] Now it needs manual testing. I'm trying to volunteer someone for it ;) [15:16:56] If I can't find anyone, i'll do it myself. but probably not today or tomorrow. ping me if it gets stuck. [15:18:13] Thanks. [15:18:15] Sure. [15:21:20] dear colleagues, i have a question about mediawiki release 1.35 and visualeditor. it looks like in the default distribution the "auto configuration" does not work for me. [15:30:38] despens: You're not alone :) [15:32:11] Vulpix: :D -- i was so happy to see visualeditor being integrated, but it worked for me in version 1.34 and the javascript based parsoid [15:33:23] If you're lucky, commenting out everything in LocalSettings that refers to RESTBase or parsoid may help [15:34:24] Otherwise, see if anything from https://www.mediawiki.org/wiki/Extension:VisualEditor#Troubleshooting works for you [15:41:12] Vulpix: yes i already erased everything but wfLoadExtension( 'VisualEditor' ); -- the troubleshooting section doesn't list the error i am getting, which is "Error contacting the Parsoid/RESTBase server: (curl error: 7) Couldn't connect to server" [15:45:46] php is trying to contact parsoid apparently. Now parsoid is a PHP library hooked into the new REST api (accessible at /rest.php). I guess it's trying to make the connection to your $wgServer URL from itself but failing, maybe because your apache/nginx server doesn't expect a connection from itself [15:46:41] (I never understood what's the point of rewriting parsoid in PHP but continue to use a connection to itself) [15:48:50] You need wfLoadExtension( 'PArsoid' ); [15:49:07] * wfLoadExtension( 'Parsoid' ); [16:02:59] i just checked, the rest url seems to work: http://localhost:8181/w/rest.php/localhost/v3/page/html/Main%20Page/144730 [16:14:29] despens: Most likely it's not using localhost but what you configured on $wgServer [16:19:01] Vulpix: the point is that the integration isn't finished yet, soon(TM) it'll just be like a normal PHP library and not talk to itself over HTTP [16:19:48] good to know [16:20:52] that sounds good. [16:21:25] in the mean time, is it possible to see the URL parsoid is trying to reach via curl? [16:27:14] Vulpix: $wgServer = WebRequest::detectServer(); -- however, it is running in a container, so when it tries to contact localhost:8181 that would be the "outside" view; from the "inside" of the container, it should be just localhost [16:28:09] i'd just like to verify that is indeed the problem before i try this on the actual deployment on the public web... [16:31:27] $wgDebugLogFile = '/some/log'; should output it [16:45:36] subbu: did we stop stripping leading whitespace, or did we never do that for leading spaces? noticed the 
 at https://meta.wikimedia.org/wiki/User:MSantos_(WMF) and not sure if that was already the case in 2019
[16:45:59] 	 I guess it makes sense to not strip, just curious if maybe it was changed unplanned
[16:47:36] 	 it was always like this
[17:00:26] 	 whitespace has been a source of so much headache ... :) but Krinkle to answer your qn. https://phabricator.wikimedia.org/T157418 should clarify where it is trimmed.
[17:00:46] 	 only for list items, headings, table cells.
[17:01:55] 	 subbu: trailing line breaks as well, right?
[17:02:06] 	 not line breaks.
[17:02:10] 	 but I guess leading line breaks and spaces on the first line are kept and perhaps even have for a long time
[17:02:12] 	 leading & trailing.
[17:02:48] 	 hm. leading/trailing white?
[17:02:51] 	 what*
[17:05:41] 	 in a meeting. chat later.
[18:54:35] 	 Krinkle, leading/trailing non-newline whitespace.
[19:02:25] 	 subbu: ok, but if regular leading spaces are stripped, then it seems they aren't on that page.
[19:02:47] 	 in general they aren't of course since leading space creates 
, but you're saying it used to or is meant to be stripped from the first line?
[19:02:47] 	 "only for list items, headings, table cells."
[19:02:51] 	 ah right
[19:02:52] 	 sure
[19:03:13] 	 T157418 has the full discussion.
[19:03:13] 	 T157418: RFC: Make some aspects of Tidy's whitespace stripping behavior part of wikitext parsing "spec" - https://phabricator.wikimedia.org/T157418
[19:04:29] 	 subbu: k, will read, but can you confirm that in e.g. last 2 years nothing has changed regarding the way first/last line breaks or first/last line whitespace is treated?
[19:04:52] 	 afaik, that is correct.
[20:15:37] 	 hey - I'm trying to link to [[Special:Addon?param=foo]]  - but the ? is URL-encoded so it doesn't work.
[20:16:06] 	 kjetilho: Yeah, you'd have to use an external link for that.
[20:16:16] 	 ok, thanks!
[20:16:31] 	 kjetilho: Or the extension that provides the special page might allow [[Special:Addon/foo]] for some cases.
[20:17:01] 	 no, it doesn't, unfortunately
[20:18:39] 	 (It was an external link already, but I like it better when "what links here" works :)
[20:20:31] 	 hmm.  there should be a bot for this ...
[20:30:39] 	 kjetilho I don't think WhatLinkHere works for Special pages at all.
[20:32:05] 	 looks like you're right
[21:30:47] 	 duesen: Thanks for the MCR feedback, got it working :)
[23:52:32] 	 I'm using the Math extension, it works for basic latex. HIs there anything that is known to work well at the momemnt for tikz?