[01:16:44] AlexZ: ^ [05:24:36] tgr: Nice work on pushing PageViewInfo forward. :-) [05:26:38] [[Tech]]; WillBo; /* Automated Temperature Conversion (template?) */ new section; https://meta.wikimedia.org/w/index.php?diff=16439607&oldid=16394927&rcid=9185764 [05:31:22] [[Tech]]; WillBo; /* Automated Temperature Conversion (template?) */; https://meta.wikimedia.org/w/index.php?diff=16439611&oldid=16439607&rcid=9185770 [14:18:10] [[Tech]]; StevenJ81; /* Global.js not loading consistently */ new section; https://meta.wikimedia.org/w/index.php?diff=16441201&oldid=16439611&rcid=9188126 [14:22:12] [[Tech]]; StevenJ81; /* Automated Temperature Conversion (template?) */ re; https://meta.wikimedia.org/w/index.php?diff=16441207&oldid=16441201&rcid=9188133 [14:35:02] [[Tech]]; Malyacko; [none]; https://meta.wikimedia.org/w/index.php?diff=16441232&oldid=16441207&rcid=9188157 [14:37:05] [[Tech]]; StevenJ81; /* Global.js not loading consistently */ re; https://meta.wikimedia.org/w/index.php?diff=16441238&oldid=16441232&rcid=9188169 [18:54:02] Hi, will somebody be so kind to have a look at T160400? [18:54:03] T160400: Request for email address seniori@wikimedia.org - https://phabricator.wikimedia.org/T160400 [19:08:08] Doesn't that need to go to OIT? [19:08:37] Reedy, what is OIT? [19:08:48] And how I can forward it to them? [19:08:48] Office IT [19:10:00] Reedy, thanks. How can I forward it to them? Do they have some specific project that should be added? [19:10:08] I've already done that [19:10:13] Reedy, thank you. [19:10:40] I'll raise it with them too [19:10:46] Reedy, thank you. [19:11:53] They may be a little busy for the next hour [19:12:57] It doesn't need to be done in next hour. But we wish to know if we may use the leaflets with wrong (forwarded) mail or we should print new ones because the forwarding isn't possible. [19:13:20] I should hope you should have a response today at least whether it's a yes or a no :) [19:13:42] That's great! [19:41:06] At nowiki we hit a limit on use of parser functions [19:41:30] It is inside a lua module, and seems to be just above the limit [19:42:04] Would it be possible to increase the limit somewhat? [19:42:44] It would be nice to support the users that is using Wikidata [19:43:50] $wgExpensiveParserFunctionLimit ? [19:43:54] It is "Expensive parser function count: 504/500" that kicks in, and a limit at 750 would probably make it pass [19:44:07] Yes, I guess so [19:44:45] https://no.wikipedia.org/wiki/Paris%E2%80%93Nice_2017 [19:44:47] Yeah, it's set to 500 in CommonSettings.php [19:45:00] jeblad: Ok, so yes, theoretically it's possible to increase it everywhere [19:45:13] It needs to go via ops and probably the performance team [19:45:16] Need to file a task :) [19:45:32] Ok, I'll write a task [19:45:45] tisk-task.. [19:46:00] >>ptisch<< [19:46:10] boomeloom… [19:46:53] Obviously say to what extent to increase it [19:46:57] 750 is a 50% increase etc [19:47:30] 2^42 [19:47:31] I'm guessing, as we don't max out the apaches to any extent, it won't be a problem... Plus newer HHVM etc coming soon too [19:48:33] That is one thing, … I'm not sure why but doing Lua testing through composer dropped the run time to 50% [19:49:26] Very strange… I believe it is due to my fabulous good work… (basically I have no idea why) [20:00:10] Reedy: It is available at T160685 [20:00:14] T160685: Increase $wgExpensiveParserFunctionLimit on nowiki - https://phabricator.wikimedia.org/T160685 [20:03:36] if you're using this many expensive functions, and the page still renders quickly, maybe they are not really that expensive and shouldn't be marked as such… [20:04:13] hmm, that pages does take 6 seconds of Lua time to render (the limit is 10) [20:04:33] so you might just start running into other limits instead. [20:07:52] Yeah [20:08:14] I suspect the gode is slightly rotten [20:08:58] Its not my code, my code is always fast… [20:09:03] * jeblad hides [20:10:58] A 50% increase in expensive functions could give a 50% increase in run time, just inside the 10 sec limit