[13:35:21] could anyone tell me what is the best way to get a full static HTML dump from the multiple wiktionaries? Can XML files be converted easily? [13:36:56] sorry, not sure if this is the right channel [13:38:14] We don't do html dumps, unfortunately [13:40:00] @Reedy I see you do it for wikipedia. Maybe I could use the same scripts to do it for wiktionary? [13:40:03] poe: talk to the kiwix people, they do this for wikipedia. don't know if they have wiktionary [13:40:20] DanielK_WMDE thanks! [13:44:35] Yeah, "we" as in Wikimedia don't actually do it :( [13:46:22] I see, they are no up to date https://dumps.wikimedia.org/ [14:12:47] tgr: Hi [14:12:52] We had asked last year an OAuth consumer for Lingua Libre, which we have hardly used because of a significant shift in the development of the project. https://meta.wikimedia.org/wiki/Special:OAuthListConsumers/view/1eee51d3553ee71cb165d77e14650421 [14:13:03] However, we would need it now, but with an other ''callback URL''. Is there a way to change it on an existing consumer, or do we need to register a new one? [14:23:29] kiwi_0x010C: You need to register a new one/new version [14:24:23] Reedy: ok, will it automatically replace the old one? [14:24:36] No.. [14:28:26] So, how can we remove then the old one? 'cause https://www.mediawiki.org/wiki/OAuth/For_Developers#Registration tell us to visit https://meta.wikimedia.org/wiki/Special:OAuthConsumerRegistration/list to do it, but once there I see no delete/disable button... :/ [14:28:52] Technical Advice IRC meeting starting in 30 minutes in channel #wikimedia-tech, hosts: @CFisch_WMDE & @Tonina_WMDE - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting [14:32:35] kiwi_0x010C: I don't think you need to [14:32:59] ok, thanks :) [14:56:05] Technical Advice IRC meeting starting in 5 minutes in channel #wikimedia-tech, hosts: @CFisch_WMDE & @Tonina_WMDE - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting [15:01:30] Hello and welcome to this week's Technical Advice IRC meeting with me and CFisch_WMDE \o/ [15:01:34] \o/ Hello! [15:02:06] So another Wednesday another IRC meeting! [15:03:02] We have no prepared topics on the wiki page so... [15:03:10] ..fire away with your questions ;-) [15:03:31] ( if there are any ) [15:04:32] what is the state of Wikidata in Wiktionary? How can we help? [15:04:38] How do we solve P=NP? [15:05:07] phfff Reedy [15:05:13] poe: whooo [15:05:18] big questions [15:05:22] :D [15:06:01] SInce neither Tonina_WMDE nor me are part of the Wikidata team [15:06:10] I am not sure about the state there [15:06:21] and where help could go to [15:06:53] maybe if Lydia_WMDE is available she can leave a note on that [15:07:21] but I would assume at least the first question is hard to answer [15:07:50] ok thanks [15:08:36] But I guess at least I can say that's appreciated that you want to help :-) [15:08:39] kiwi_0x010C: there is no self-disable ATM, admins can disable it for you [15:09:24] although it is indeed not needed (consumer versions are just UI sugar, every version is a separate, unrelated app basically) [15:12:08] poe: that might be helpful https://www.wikidata.org/wiki/Wikidata:Lexicographical_data [15:12:50] I was looking at that, apparently they will deploy the first version this month [15:14:06] yep, looks like it [15:18:23] Sooo anyone else? :-) [15:31:43] CFisch_WMDE: we consistently run into issues regarding Lua memory on our project. Is there anything in the works to help diagnose or resolve such issues? Or to help module developers understand the impacts of their changes before making them live? [15:32:32] Hi TheDaveRoss [15:33:15] I am not sure about that ... [15:33:35] ...but let me dig around a bit to see what I can get. [15:36:51] So I guess you're using https://www.mediawiki.org/wiki/Extension:Scribunto [15:37:20] there is a setting for lua [15:37:22] yes, it is a WMF wiki (en.wiktionary.org) [15:37:23] memoryLimit [15:37:43] i.e. we have limited control over such settins [15:37:58] ah ok [15:38:21] so I am not sure if that setting would apply for the WMF production servers [15:38:41] but if so it could be changed by the operations people [15:38:42] there is a lua profiler that can help track down expensive modules, but I don't know where its functionality is documented [15:39:15] TheDaveRoss: You could also start by creating a ticket stating the problem [15:39:57] We generally rely on inspecting the source to see where the memory is going, but it is hard to understand from a lay perspective how the memory usage is calculated and when modules can recycle memory etc [15:40:01] and if increasing that limit might be a first solution, devs could start working on that [15:44:40] TheDaveRoss: there's something on phabricator regarding the problem https://phabricator.wikimedia.org/T188492 [15:47:12] Yeah, it has been a persistent issue for a couple of years, I mostly suspect it is how we use modules but we don't have a lot of guidance on how we should be using them [15:57:16] Hmm I dug a bit but also could not find satisfying answers for LUA performance issues or profiling. ... So it seems you could profile things when testing them in the sandbox ... [15:57:21] but I did not get how. [15:57:52] I you might want to post something on https://discourse-mediawiki.wmflabs.org/ [15:58:17] for a broader audience [15:59:59] is there any public page like https://tools.wmflabs.org/admin/oge/status where one can see if there is a replica lag? [16:00:54] right now the lag seems to be >24h [16:01:14] seth_unr: o.O [16:01:30] (or I am just too dumb) [16:02:19] you should probably ask in #wikimedia-operations ... I mean for the lag [16:02:29] ;-) [16:02:54] ok [16:04:31] CFisch_WMDE: i think that's more #wikimedia-databases and #wikimedia-cloud heh [16:04:58] seth_unr: ^ [16:06:23] Hmm yeah right - so many channels ^^' [16:06:48] i agree there are many channels [16:06:53] but seems operations did work [16:06:55] :-) [16:07:07] win 41 [16:08:11] So official time for the technical advice meeting is up. See you around and maybe next week! [16:08:16] \o/ [16:08:29] Thanks everyone! See you! o/ [16:14:43] thanks, yesm -operations worked [16:14:58] s/m/,/ [16:15:00] :-) [18:27:52] hm, CI fails with 18:13:22 Error: your composer.lock file is not up to date. Run "composer update --no-dev" to install newer dependencies [18:27:57] that shouldn't happen, right?... [18:28:19] Maybe [18:28:30] Depends if the vendor patch merged before core and stuff [18:29:07] Or a rebase might be needed [18:29:09] well, the patch in question doesn't touch composer.json [18:29:22] Doesn't matter [18:29:25] hitting rebase now [18:29:37] If your patches parent is an older composer.json... and the one in vendor has changed [18:29:41] There's potential for mismatch [18:30:11] yea, i see [18:30:18] could use a better error message [18:30:59] any, ttfn