[00:31:52] James_F, re: re-announce - it's a quiet week, so yeah, seems worthwhile. I'll add. [06:03:23] Hey, can someone tell me what to do in rearguards to this: http://i.imgur.com/eLkayyK.png [06:03:32] See the {{helpme}} in the lead. [06:04:48] That's https://en.wikipedia.org/wiki/User_talk:Yogesh_Khandke you mean. :) [06:05:20] Yes, yes, sorry. [06:05:26] Clipboard shenanigans. xD [06:05:50] :) [11:10:49] Could someone with shell access please look up exception f3194391 on Commons and paste that into https://phabricator.wikimedia.org/T129637 ? thanks in advance [11:55:52] hi [11:56:08] the 'jobs' count is increasing constantly, I don't know why it is happening https://pl.wiktionary.org/w/api.php?action=query&meta=siteinfo&siprop=statistics&format=xml [11:57:24] I started a purge on a template transcluded on every page in that project, but it has exceeded the total number of pages [11:57:57] PeterBowman: https://phabricator.wikimedia.org/T129517 [11:58:33] oh, thanks, Glaisher [12:33:33] andre__: exception log is nearly 3G, gonna take a while... [12:33:57] Or not find anything [12:34:01] * Reedy gurumbles [12:36:48] urgh [12:36:54] Reedy, but thanks for trying [12:36:57] meh [12:37:27] it should be in the current active logs, as it was only 90 minutes or so ago [12:37:35] I did zgrep for recent archived ones [14:39:53] hi [14:40:21] there is an important cache/delay issue on WS https://fr.wikisource.org/wiki/Livre:Baker_-_Pourquoi_faudrait-il_punir,_2004.djvu [14:41:06] I finished this book yesterday, and the pages are still shown in yellow [14:41:31] any idea what's going on? [14:41:41] should I open a report? [14:41:56] yes the job queue is currently busted [14:41:59] https://grafana.wikimedia.org/dashboard/db/job-queue-health [14:43:18] see https://phabricator.wikimedia.org/T129517 [16:29:07] hi, where can I find a list of messages loaded by default and accessible through JS? (mw.messages) [16:29:22] such as 'ok', 'cancel'... https://www.mediawiki.org/wiki/Gadgets_2.0#Defining_messages [16:45:50] PeterBowman: there aren't any. [16:46:08] if you see them, it's only because something else luckily loaded them first. [16:46:42] PeterBowman: but you can use new mw.Api().loadMessages(...) to load them, IIRC. (requires a dependency on 'mediawiki.api.messages') [16:47:27] maybe it's some initialization script, then? I don't see 'cancel' on https://git.wikimedia.org/blob/mediawiki%2Fcore.git/HEAD/resources%2FResources.php [16:48:08] any of the billion extensions and jillion gadgets could have loaded it. [16:50:52] hm, it seems a bit risky to use them without relying on the API [16:50:57] thanks, MatmaRex [16:52:56] closedmouth, andre__ thanks for the info [16:53:03] do you the reason for that? [16:53:11] *know [16:55:00] yannf, see the bug report [16:55:44] oh, btw MatmaRex - https://www.mediawiki.org/wiki/API:Options [16:55:54] There are currently no hard limits on the length or contents of the value, nor is there a limit on the number of user options you can set [...] [16:56:12] do you know what a reasonable limit would be? [16:56:37] I'd like to store templates for wiktionary entries [16:57:45] PeterBowman: these are always send in page HTML, so… short [16:57:59] andre__, wow this looks far more serious than I thought [16:58:21] PeterBowman: there's actually a hard limit, but it's something ridiculously large like 64K or something - it's just the size of the database field [16:58:33] always sent* [17:00:06] hm ok, perhaps it's better to read/store json data on-wiki, maybe on some user subpage [17:01:45] 4 times the maximum in January [17:02:01] the last time this happened [19:05:12] andre__, job queue still growing at the same rate... [19:12:53] yannf, well, not much I can do. :( See the people who have commented on the task in Phabricator... [20:52:25] @Krinkle: Does wikipage.content fire before or after Gadgets are loaded? [20:53:01] kaldari: Doens't matter since it's a mw.hook, which means, similar to $(), it will call immediately if the hook fired before registering [20:53:41] OK, in that case, it's not a good substitute for postEdit for Gadgets [20:54:03] kaldari: Why? [20:54:28] kaldari: It fires for page content. Once on initial load and whenever the content has been swapped (e.g. after live preview or after VE) [20:55:10] Some are using the postEdit hook to reload after a VE edit, not to do the initial load. (Although they could be refactored to use wikipage.content for both) [20:55:58] It would be nice though if there were a hook that could be used for when VE rebuilds a page [20:56:23] kaldari: What is the use case for doing something only after edit,including after null-edit, but not on initial load? [20:57:18] Can some take a look at https://sr.wikipedia.org/wiki/MediaWiki:Edittools ? The row that contains [], [[]], [[|]] and other chars doesn't insert them anymore but instead just goes to the top of the edit window. [20:57:33] There is no use case for that. The gadgets were written before VE existed. [20:58:22] kaldari: And they used postEdit because it was an unrelated random hook that happened to fire in one of cases where the gadget didn't work as expected so they tapped into it. and now there is more random cases where the gadget doens't work and we request extending the random hook we're already using :D [20:58:42] basically :) [20:58:48] Assuming the gadget changing the page in some way (e.g. similar to mediaviewer or tablesorter) it is destined for wikipage.content. [20:59:00] understood [20:59:02] It would suffice in all scenarios, including the initial load and any other one. [20:59:12] If it fires too often or too little, by all means, let me know :) [21:00:17] postEdit is effectively a subset of wikipage.content and that will continue to work for that subset of cases, but firing it when there wasn't an edit will just cause bugs elsewhere. And it sounds like this gadget will end up cleaner with wp.content by only having to hook into one thing (instead of domready + postEdit) [23:37:27] kaldari: Re: postEdit. Be sure to consider the parameters passed to the hook as well. wikipage.content has $content as parameter. It's a hook, not an event (e.g. notif with data, not a notif to re-inspect the global document. additionally important as hooks may fire off-screen before the paint happens in the browser) [23:37:41] E.g. visualeditor prepares the document and then inserts it at once to avoid FOUC and reflows [23:37:59] (you want to hook before the rendering not after, best for the user)