[00:15:21] irc.grepnet.org #chats - world's TOP HACKER IRC, even Edward Snowden is there, connect NOW or you're a loser. [00:18:43] hi ppl. I have a question about this warning: "{'warnings': 'This result was truncated because it would otherwise be larger than the limit of 12,582,912 bytes.'}" . There is a way to overcame this limitations? I found some phab tickets, but no concrete solution. [02:56:13] An error occurred: an invalid token was found. [02:56:34] I'm trying to setup openid because I can't use openid connect with steam [02:57:25] $wgOpenIDProviders = array( 'Steam' => array( 'large-provider' => true, 'openid-url' => 'https://steamcommunity.com/openid/id/' )); is what I have in openid.php [02:58:01] require_once( "$IP/extensions/OpenID/OpenID.php" ); $wgTrustRoot = "https://domain.com/"; in localsettings.php [02:58:43] I have an API key not sure where to plug it in [05:00:58] uhm, I'm not sure whatever I really should do redirects to allow namespaces to work without causing httpd to produce harmless errors [05:02:00] namespaces such as special, on Windows, the specific issue is the : having special meaning in Win32 [05:02:45] it thinks the url is malformed or contains invalid characters [05:03:29] the issue appears to have been often experienced under mediawiki [05:18:17] what web server are you using? [05:26:10] apache httpd, TimStarling [05:27:01] maybe there is something unusual about your configuration that causes it to give errors [05:27:34] not sure, it's a copy of xampp [05:27:44] yes I'm aware of the security implications [05:28:07] have you got a /wiki/ alias? [05:28:25] no, do i need one? [05:28:38] the issue is : symbol specifically [05:28:52] in URLs like /index.php/A:B ? [05:29:02] yeah [05:29:53] you could try a path to query rewrite rule [05:30:17] rewriting /index.php/ to /index.php?title=<title> [05:30:55] <TimStarling> or better, /wiki/<title> to /index.php?title=<title> [05:31:06] <TimStarling> with $wgArticlePath = '/wiki/$1'; [05:31:34] <TimStarling> my feeling is that if you had such a rewrite rule, it wouldn't need to consult the filesystem [05:37:57] <Juesto> ah right [05:38:24] <Juesto> my folder is 'mediawiki' [05:39:44] <Juesto> does it apply to all namespaces including special: ? this sounds more of a workaround rather than a solution TimStarling [05:40:48] <TimStarling> I don't know if it'll work, but if it does, it would apply to URLs containing colons generally [05:41:00] <TimStarling> the best solution is to not use windows, that is a very rare platform for mediawiki [05:42:03] <Juesto> I don't mind plus it's a experiment test setup for myself to learn [05:42:18] <Juesto> i suppose it's not necessarily a huge concern then [05:45:45] <TimStarling> I used to run MediaWiki on Windows originally, in about 2003-2008 [05:47:29] <TimStarling> I fixed a lot of relevant bugs at the time, introduced wfIsWindows() [05:48:26] <TimStarling> I don't know if it's really worth bothering with these days, with hardware being so many times more powerful, it's much more feasible to run MediaWiki in a VM [05:50:15] <TimStarling> I wonder how much RAM I had back then [10:20:49] <justinl> Hi all. I have a user reporting that in our upgraded 1.34 wikis, Special:Upload is causing a newline to be prepended to the wiki text of the license when you select a license from the dropdown as opposed to it being correct when manually entering in license text in the summary box. I doubt this is a config issue, so I wanted to try to verify that [10:20:50] <justinl> this may just be a bug in MW rather than an issue specific to us. [10:28:04] <justinl> Separately, I'm still trying to figure out what all of these "explicit transaction still alive" / "deadlock found" errors are about. They keep happening on certain of our wikis (the larger ones) when running rebuildData.php, whether to do full rebuilds or just deleting outdated entities. Here is the full output of a script crash: [10:28:05] <justinl> https://gist.github.com/justinclloyd/91d54bbe88fa738ead1d26fdabed9099 [14:39:03] <Yaron> Hi - given the name of a file that's been uploaded to the wiki, what code can you call to get its path, like "/a/ab/MyImage.png"? [14:46:44] <andre__> Yaron: Sounds like https://phabricator.wikimedia.org/T66214 or https://phabricator.wikimedia.org/T139294 [14:48:47] <ashley> Yaron: wfFindFile(/* or whatever its tl,dr services equivalent these days is */ $title )->getUrl() ? [15:49:15] <Yaron> ashley: thank you! Sorry I didn't respond before. I'll try this out soon. [16:03:43] <tillmarks> Hi guys, I have a special category on the wiki. And every page in that category is linking to a second page. Now I want to check the second page if it has a special tag. What would be the easiest and best way to do it? Does anyone an idea? [16:08:24] <Vulpix> tillmarks: with the api you can get in one query the links to those second pages (using categorymembers as generator, then list links of those pages). Once you collect those page titles you'll need to query the api again to get the text and manually find the special tag within the text [16:08:33] <Vulpix> You'll need some scripting to do that [16:09:57] <tillmarks> ok so I have to make a script for it [16:10:36] <tillmarks> Vulpix thank you. Is there a good tutorial for that? Only if you know. I will google for it [16:40:56] <justinl> I have a question about patching MW. I want to update from 1.34 to 1.34.1, normally in the past I'd have just applied the patch file to each of the 7 wiki dirs under /var/www/sites and then rsync'ed that to all the wiki web servers. However I have a script that builds a new /var/www/sites directory from scratch (primarily via git clone and php [16:40:57] <justinl> composer) based on a git branch name, i.e. REL1_34. So if I run that now, I get a completely updated 1.34.1 directory, that I can then move to /var/www/sites and run my rsync script. Any reason to use patch over a completely new tree? [16:41:31] <Skizzerz> faster? [16:41:39] <Skizzerz> but the end result should be the same [16:42:46] <justinl> Speed isn't a concern for me, so that's not a problem. I figured the end result should indeed be the same. But the difference is newer versions of vendor libs, extensions, etc. that aren't a part of a core mediawiki patch like this. [16:44:16] <justinl> I do have matching dev and live environments, so I can test and even revert since I keep my /var/www/sites directories that I build and use live, .e.g /mnt/build/sites.REL1_34.20200325, for example, so I can just move the old one back into place and re-deploy with the rsync script. Seems safe to have that rollback plan, just wanted to be sure I [16:44:16] <justinl> wasn't overlooking something important. [16:45:50] <Skizzerz> you're overlooking something rather minor, which is that the head of the REL1_* branch may not necessarily correspond exactly with the latest point release [16:46:02] <Skizzerz> there may have been additional backported fixes since the latest release present in that branch [16:46:28] <justinl> That's the sort of concern I was thinking about. [16:46:28] <Skizzerz> if matching 100% is your goal, using tags instead of branches is probably wiser [16:46:46] <Skizzerz> but having additional fixes probably won't hurt anything :) [16:46:57] <justinl> Probably, but that's why I have a dev env, too. :) [16:47:42] <justinl> Good point about tags, though, let me look there. I did just check a diff of my REL1_34 build from last month vs. one done today and I don't even see the patch stuff in there. [16:50:22] <Yaron> ashley: thanks, that worked! Well, what I needed was getUrlRel(), but close enough. [16:51:31] <ashley> :) [16:54:04] <justinl> Skizzerz Hmm, I delete the .git directories after building the sites dir, so I don't have tag info, and just downloading a 1.34.1 tarball would be more effort than just applying the 1.34.1 patch to existing directories. Maybe I'll update my script or write a new one to handle such a patching process. Thanks for the feedback! [16:55:47] <Goooodman> Please, how do I create a 404 page that would redirect someone from example.org/x to a.example.org/wiki/x ? Like we have on www.wikipedia.org [16:58:35] <Goooodman> . [17:01:18] <Goooodman> . [17:01:54] <andre__> Goooodman: Please stop posting lines with only one character. Thanks. [17:03:20] <Goooodman> Oh! I'm sorry, I'm just trying to keep the chat window busy until reply come otherwise, it would disconnect. [17:03:52] <Goooodman> Do you understand my question? [17:04:59] <andre__> Which broken chat client would disconnect in case of no replies?! [17:10:52] <andre__> Goooodman: See stuff like modules/mediawiki/manifests/errorpage.pp or modules/mediawiki/templates/errorpage.html.erb in the operations/puppet repository but as you already impatiently left you'll probably never see this reply. [17:11:42] <Reedy> I can't work out why it's anything more than an apache rewrite rule :P [17:12:38] <andre__> that too, I thought they were after the shiney shiney parts [17:30:01] <Vulpix> tillmarks: Sorry. I was away. Choose the language you're most comfortable with. I usually use JavaScript on the browser's console directly [19:52:07] <ottomata> Krinkle: o/ [19:52:09] <ottomata> :) [19:52:25] <Krinkle> Hi [19:52:34] <ottomata> thanks for quick reviews! [19:52:49] <ottomata> what I meant by no longer just schemaRevision is described in the commit message [19:52:52] <ottomata> it can now be [19:52:57] <Krinkle> yw :) I'm currently doing some boring user js find/replace fixes over all wikis. [19:53:14] <ottomata> MySchema: "/path/to/myschema/1.0.0" [19:53:40] <Krinkle> ah okay, without the context of the commit it reads as if it changed from int to array<string,int> [19:53:42] <ottomata> schemaRevision is just not an accurate name anymore so I added the comment. wonder if I should change the name? [19:53:55] <ottomata> oh [19:54:12] <Krinkle> feel free to rename that. it's privately bundled with the JS code, they are always atomic together. [19:54:20] <ottomata> ok great [19:54:36] <ottomata> in core.js i changd the function name to getRevisionOrSchemaUri [19:54:49] <ottomata> should I call this schemaRevisionOrSchemaUri ? [19:54:51] <Krinkle> just 'schemas' might also work :) [19:54:55] <ottomata> ok [19:55:02] <Krinkle> but yeah, I like the new docs [19:55:05] <ottomata> schemasInfo [19:55:05] <ottomata> ? [19:55:34] <Krinkle> sure