[01:46:36] Which components of Extension:ScheduledCacheExpiry are impacted by commit 3ba2dc9 ? I'm asking here since only people who often read this channel might know. [01:47:19] (Gerrit isn't loading for me, so if there's any information in the commit itsself I can't see it.) [01:48:58] Should I ping CA/UO? [01:51:18] cacheinterval mostly. It can't be lower than till next midnight, so any cache lower than till next midnight wont work but we are planning to patch core on our end to fix this. [01:53:08] Thank you [01:53:33] Is next midnight UTC, wiki time, server time, or user timezone? [01:53:49] UTC I believe. [01:54:31] But we will patch this within the next couple days to make it not an issue for us. [01:55:11] Got it [01:56:10] You add so many features to MediaWiki. Huge thank you for making this and other patches/extensions/etc. [08:25:18] [1/2] didn't notice till now, this is cool [08:25:19] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1553321557043052675/image.png?ex=6ab8d2ee&is=6ab7816e&hm=39415eddcc829f2593acc41daae119b000d1b323baedb9245fd8bd7c58fa9a24& [08:25:34] that's a 1.46 thing? [08:41:12] isnt this how it normally is [08:41:15] or am i crazy [08:43:21] if it is then that's a big til for me [08:43:41] maybe the fact it doesn't pop up in recent changes and I generally don't check for that put my blinders on [08:43:58] pretty sure its always been like that (some1 fact check) [08:44:29] if its been literally always then I'm tripping hard [08:44:40] if its older than like 1.45 I'll be sad [08:54:10] i think it's 1.45 or 1.44, not sure [08:54:19] it used to be from [list] to [list] [08:54:50] but not a new thing in 1.46 either [08:56:37] if it was 1.44-1.45 I could see myself just missing it for that long [08:57:00] I generally have no reason to go look at rights log after doing a global assignment like that [09:09:40] i think some types of logs in our managewiki can also be updated to this format [09:09:48] this does improve readibility [09:21:44] that's what I really want to see [09:22:31] certain global actions reflected outright on wiki and also vice versa: stewards can reopen locally and it gets logged globally and so that solves that problem without whatever wizardry is on the permanent backlog required to make central reopening reset dormancy locally [09:23:54] [1/2] the problem left for me looking at it that way is how do you separate the steward doing central business from I am a steward but also a local admin and not needlessly logging the latter. It can be a flag but if its a flag you have to explicitly press (might be better to unpress?) then that's room for error and also if someone goes rogue that way then the accountability mechanism is e [09:23:55] [2/2] asily defeated [09:40:02] i just noticed we're not talking about the same thing. i thought you were saying how the message is phrased [09:41:52] i mean the 'granted check user' used to be ' from (none) to check user' [09:42:48] i've no idea about the global log thing [09:50:41] oh, yeah, didn't even look there [09:50:52] phrasing update could be nice I'm sure [10:02:55] yes. it's updated to such `granted A; revoked B; kept C unchanged` in a recent version, which used to be simply `from B and C to A and C` [10:04:42] log for ManageWiki/permissions also often has many (none) sentences so i was suggesting if they can also be omitted [10:16:26] The i18n message is written as a full unit https://github.com/miraheze/ManageWiki/blob/37a186125a1043dda0cbd71ef039d6a051834a30/i18n/en.json#L55 so you either need to do some processing on PHP's side (probably impossible because the semicolon corresponds to different things in different languages) or the message needs to be split. [10:17:33] exactly, the core split the rights log message to achieve this [12:43:57] I think it's 1.45 [12:44:16] but I skipped 1.44 because I couldn't be arsed and also because by the time I got round to it 1.45 was out [16:28:47] Hi, I would like to request help about miraheze wiki account issue\ [17:09:29] KyoriAsh: hi [17:09:44] I will look at your account now [17:13:43] Oh thanks [17:14:01] KyoriAsh: can you check your email? [17:14:01] The issue is I didn't receive the random password from the email [17:14:07] Oh ok [17:14:10] let me check [17:14:39] I can explain in DM why you didn't get the random password [17:14:40] OK now I received [17:15:35] KyoriAsh: glad to be of assistance :) [23:31:30] [1/4] https://cdn.discordapp.com/attachments/1006789349498699827/1553549608838504560/image.jpg?ex=6ab9a752&is=6ab855d2&hm=cea6c7f65e7ed3a8585ce7fda7f9e9b7eada5b501aa6e754f5b258a1af26053b& [23:31:31] [2/4] https://cdn.discordapp.com/attachments/1006789349498699827/1553549609241149522/image.jpg?ex=6ab9a752&is=6ab855d2&hm=5cf7752d6ce5bb655dbbb885088205b38aeb8b65cae8cbff10c613bbec252ef4& [23:31:31] [3/4] https://cdn.discordapp.com/attachments/1006789349498699827/1553549609664782376/image.jpg?ex=6ab9a752&is=6ab855d2&hm=f67cbd5c19a69be04e920cfce1be4f6fb92b4996b9ebc220091b699e186a88cb& [23:31:32] [4/4] https://cdn.discordapp.com/attachments/1006789349498699827/1553549610079752373/image.jpg?ex=6ab9a752&is=6ab855d2&hm=e152eda98dc8d0bda78df1708b61d830b7f1c52e346c69e6f8d9d6ab0389f666&