[07:15:15] i'm here like "it's been over 24 hours since i made https://issue-tracker.miraheze.org/T12670, why is the patch not merged yet" [07:58:25] BlankEclair: Do you have access to open a security incident for it? I'm not sure if you do. [07:58:34] nah [07:58:44] I'll jump on IRC, can you PM for a min? [07:58:52] sure [08:55:18] CosmicAlpha: i'm back btw [09:09:18] CosmicAlpha: tempted to get irccloud just to fix its notifications [10:10:51] pixldev: i got an answer: https://we.phorge.it/Q155#A191 [10:10:55] do you want me to look into it?> [18:21:20] can I open an old localsetting.php related task, to request an additional change to it? related to the same extension [18:43:57] or it's better to open new?.. [19:36:22] New [19:36:36] Tasks should be 1:1 [19:36:43] 1 request in 1 task please [19:37:02] And once they shut, they should only be reopened if the task wasn't done / didn't work [19:37:19] If you need similar / same change on a wiki, new task [19:37:25] If it breaks in future, new task [19:39:35] aight [20:09:54] I think personally if the same error reoccurs closely after the original task should be reopened [20:13:51] That would fall under task didn't work [20:14:17] In the future means like actually in the future [20:14:38] If the same error reoccurs closely after the original task, our fix didn't work [20:38:21] [1/2] I been having an issue with the move command despite being an admin it gives me this error https://greatcharacters.miraheze.org/wiki/Special:MovePage?action=submit is their anything you know that is causing this issue [20:38:21] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1291137218081063044/IMG_0294.png?ex=66ff00bc&is=66fdaf3c&hm=b67bb118864456cc21079fe29812b1b18e8bf7cec4f8ccc972f6f79313c0db40& [20:38:53] Have you changed permissions recently [20:41:38] I am an admin [20:41:45] And I can’t even change any permissions [20:41:58] On the manage wiki thing as I am not top admin [20:42:04] What's your username [20:42:18] 339Breakingoof [20:43:23] I have seen something weird [20:45:06] Hmm [20:46:09] I know what's caused this [20:46:13] But not why [20:49:35] It like happened one day for some reason which I don’t know how that weird thing happened like I was just minding my business and then started seeing the icon gone on my bar and other users messaged me about this issue [20:58:51] We're aware of the issue and working to fix it [20:59:19] I'll kick the cache for one [21:00:18] I will say however @yoshi459292927370272: ```Due to the ongoing issues the best thing to do is to contact any of the tech team until they take action or the issue of the page making permission has been fixed.``` this is not necessarily a good thing, ideally one person representing the project (like yourself) reports as needed [21:00:43] it would be messy of several people suddenly came in clamoring between each other about the same issue, and you know well how rowdy people can get especially off a reception wiki [21:01:47] in about 15 minutes from this message, try moving again and seeing if it works [21:03:57] Ok then [21:04:11] Tech won't help you move pages [21:04:21] Either ask a confirmed user, crat or steward [21:04:27] We will fix the bug shortly though [21:04:29] It's a data issue [21:06:25] Thanks for the fix [21:07:17] cc RhinosF1, a quick fix for this is a steward takes a trip to Special:ManageWikiDefaultPermissions and refreshes createwiki cache [21:09:50] Also for the site notice I will remove it now that the issue is getting worked on and a quick fix has been provided [21:16:53] We explicitly decided not to do that immediately [21:17:09] We wanted to see if the dodgy user right appeared in ManageWiki and could be removed [21:17:15] And then the correct ones added [21:17:20] Before completely resetting it [21:17:24] See Mattermost [21:19:39] But if you've already done it then shrug [21:19:40] I have no access to mattermost [21:20:00] Oh ye stewards don't have that [21:20:07] @raidarr have you done the reset [21:20:30] I have done it already yes [21:20:35] Okay [21:20:56] In future, if tech say we're working on it, we may be trying to debug stuff or want to check things [21:21:35] this is why I wanted a tech backchannel on the community roles server so some cross contact on this could be forwarded [21:22:03] I mean generally if we say we're working on something, ask us before you do anything else [21:22:10] though being absent from core channels means I/any strictly steward type will permanently be on the backfoot [21:22:25] I thought it might have been possible to fix this without a complete reset [21:22:48] I assumed by working to fix it I thought you were talking about clearing up the cache problem in general terms that has lingered on many wikis despite it originally being earmarked as a small issue [21:22:58] so I'll keep that in mind next time it appears for this [21:22:59] But unless you went to ManageWiki/permissions first to check then no idea if it would have worked [21:23:09] @raidarr do you know what the actual bug was? [21:23:22] I never heard the technical explanation of the original bug that caused it all no [21:23:53] @raidarr we havent found an underlying cause but Special:ListGroupRights was showing 'createaccountcreatepage' instead of the two rights separately [21:24:04] It seemed to have merged 2 rights into one for some reason [21:24:11] I'm not aware of that happening before [21:24:17] now that you mention it I think I saw something like that being discussed [21:24:24] If that has happened before, that's very interesting [21:24:28] didn't retain much about it [21:24:59] But ye resetting it will fix it at the expense of any other changes they made [21:25:06] It's a weird one [21:25:15] you might be misunderstanding what I meant by refreshing the cache [21:25:38] unless you're referring to changes they might have made in the immediate moments before the issue and not the overall changes of the wiki in permissions [21:25:56] or have I missed an in between on this [21:26:02] Special:ManageWikiDefaultPermissions will overwrite any custom changes to permissions won't it? [21:26:55] the page name is misleading [21:26:57] https://cdn.discordapp.com/attachments/1006789349498699827/1291149448734445630/image.png?ex=66ff0c20&is=66fdbaa0&hm=8708c982637587a8bfe68824991821f1bfc8b6fa4e2f102626f8e5e9b95e3d7a& [21:27:09] the third button is what resolves the issue and does not have lingering consequences that I know of [21:27:14] if it was the first two then yes [21:27:41] That's interesting [21:27:53] Now that would have been extremely useful to have debugging data on [21:27:58] this is the option found and prescribed for the issue some time ago [21:28:06] Cause that could have even just been on a single mw* [21:28:15] I have no issue collaborating with tech for timing if we see the issue again and want to test [21:28:36] How many times has this happened before? [21:29:04] And has it been recent? [21:29:05] Cause that gives me more questions [21:29:14] I wonder if something went wrong when we did the cache changes [21:29:20] If it's recent [21:29:26] it is recent [21:29:35] Which could be a bug we've already fixed but lingering issues [21:29:36] my sense of timing is horrible but it can't have been more than a couple weeks [21:29:50] Ye please report these issues to tech [21:29:55] my understanding is that it was already fixed at its core by @agentisai, but various wikis are still experiencing cache issues [21:30:02] this matter was already discussed with him ie tech [21:30:06] I'm not actually sure why we expose that button to stewards [21:30:09] it seems to me there is some core communication missing [21:30:17] You shouldn't ever need to press it [21:30:22] Or something is going wrong [21:30:37] But if this is broken on a few wikis, I think we've fixed it happening on any more [21:32:00] It was broken but shouldn't be anymore [21:32:12] I have been addressing/observing lingering reports of this [21:32:28] sometimes it appears to go away on its own, or someone has pressed the button and I did not hear about it [21:32:29] It was caused by a very wide SQL query but the table was rolled back to its state before that happened [21:32:38] it's likely a poisoned cache [21:32:54] @agentisai can we please do a global cache reset [21:33:10] is there/would there be an incident report about this [21:33:30] @raidarr there should be yes [21:33:34] oh and rhinos, https://discord.com/channels/407504499280707585/407504500136607745/1288522695146733638 [21:33:45] Data corruption should trigger an automatic incident report [21:33:51] the following message was after agent's fix [21:33:57] Okay [21:33:59] but cache issues lingered since [21:34:00] the table was only borked for a few minutes so I didn't expect it to require an IR [21:34:08] Ye I have no idea why we didn't do a cache reset after [21:34:13] but it seems the cache lingers [21:34:13] it's probably reached the point of one [21:34:14] To learn lessons [21:34:22] also to document stuff [21:34:43] I mean the lesson here primarily is managewiki is a mess in the backend [21:34:59] But at least a minimal incident report would be useful [21:35:24] The biggest question being why we didn't notice the full impact and do a cache reset for over a week [21:37:14] @agentisai resetWikiCaches needs to be done on every server doesn't it? [21:37:52] no, only one [21:38:21] Cool [21:38:26] Oh I remember [21:38:38] Its server specific cache but you can trigger an update running on one [21:39:07] I'm going to go to bed [21:39:21] This might be one of my case studies for the cyber assurance work coming up [21:57:48] https://issue-tracker.miraheze.org/T11716 [22:02:44] thank you, opined there [22:07:30] I forgot about that. Should we go with an alias or a total rename of the main special page to something that better covers both? (which btw I never liked it's name as it's to long IMO lol) [22:08:18] I think it may aswell just be a renamed, although I'm not sure what it would be renamed to [22:09:07] I like ManageWikiDefaults as it being just the name [22:09:26] retains the purpose, snappier and includes the more extended uses [22:10:06] I don't mind that name either [22:11:22] For now I may just add ManageWikiDefaults as an alias while we kinda phase it in before renaming the page itself [22:11:39] Then swap it so the old name becomes the alias [22:13:27] sounds reasonable [22:19:30] They're very handy buttons and save workload from tech, so definitely appreciate them existing with an easier URL