[00:39:37] @cosmicalpha Good timing for mirabeta's upgrade because I just made https://issue-tracker.miraheze.org/P607 [00:40:10] Nice thanks! I am just checking SQL and scripts before i do full upgrade on beta. [00:40:35] And I think we should move our tracker for extension testing elsewhere. Maybe to a dedicated extensions wiki on prod because the current one on Phorge is just terribly difficult to edit or do anything about it in general. [00:40:50] [1/5] We need to look what these do which aren't on the 1.47 task yet and not sure if we need to do anything with them: [00:40:50] [2/5] ``` [00:40:51] [3/5] /srv/mediawiki-staging/1.47/extensions/Echo/sql/mysql/tables-push-generated.sql [00:40:51] [4/5] /srv/mediawiki-staging/1.47/extensions/UrlShortener/schemas/mysql/legacy.sql [00:40:51] [5/5] ``` [00:41:21] exttest works too but it'll need to have bucket enabled at all times since the list will likely be generated by a bucket query, plus it can be down whenever bad things happen during testing [00:45:14] First one is in a +500 diff: https://github.com/wikimedia/mediawiki-extensions-Echo/commit/dd3502fa35c835403b613696e5a67fa42a6231fa [00:45:35] Seems necessary if we want to use virtual domains? [00:49:18] Maybe. [00:49:37] [1/17] Also @posix_memalign need to investigate if any of these are needed or not: [00:49:37] [2/17] ``` [00:49:37] [3/17] /srv/mediawiki-staging/1.47/extensions/CentralAuth/maintenance/DemoteIneligibleCentralUsers.php (Maintenance) [00:49:38] [4/17] /srv/mediawiki-staging/1.47/extensions/CentralAuth/maintenance/RecalculateGlobalEditCountForUsers.php (Maintenance) [00:49:38] [5/17] /srv/mediawiki-staging/1.47/extensions/GlobalPreferences/maintenance/SetGlobalPreference.php (Maintenance) [00:49:38] [6/17] /srv/mediawiki-staging/1.47/extensions/OATHAuth/maintenance/Enable2FAForUsersWithout.php (AllUsers) [00:49:39] [7/17] /srv/mediawiki-staging/1.47/extensions/OATHAuth/maintenance/FindWebAuthnKeysWithDeprecatedAlgorithms.php (Maintenance) [00:49:39] [8/17] /srv/mediawiki-staging/1.47/extensions/OATHAuth/maintenance/ForceLogoutUsersNotMeetingTwoFactorRequirements.php (AllUsers) [00:49:39] [9/17] /srv/mediawiki-staging/1.47/extensions/OATHAuth/maintenance/NotifyTwoFactorRequired.php (AllUsers) [00:49:40] [10/17] /srv/mediawiki-staging/1.47/extensions/OATHAuth/maintenance/ReEncryptSecrets.php (Maintenance) [00:49:40] [11/17] /srv/mediawiki-staging/1.47/extensions/OATHAuth/maintenance/Recover2FAForUser.php (Maintenance) [00:49:41] [12/17] /srv/mediawiki-staging/1.47/extensions/OATHAuth/maintenance/Base/AllUsers.php (Maintenance) [00:49:41] [13/17] /srv/mediawiki-staging/1.47/extensions/OAuth/maintenance/ManageConfigurationBasedClient.php (Maintenance) [00:49:42] [14/17] /srv/mediawiki-staging/1.47/extensions/WikibaseQualityConstraints/maintenance/CreateEntitiesWithConstraintViolations.php (Maintenance) [00:49:42] [15/17] /srv/mediawiki-staging/1.47/maintenance/applyChangeTag.php (Maintenance) [00:49:43] [16/17] /srv/mediawiki-staging/1.47/maintenance/reportObjectStashStats.php (Maintenance) [00:49:43] [17/17] ``` [00:51:56] But I think I should be okay to do beta now. We can run later if we decide we need to. But most I don't think we do? [00:51:57] Most of these don't seem necessary fortunately. Just a lot of new utilities. [00:52:54] I don't think there would be an important maint script without sql patches anyway? [00:53:10] [1/2] Was thinking whether I should do this through the normal extension request process or use my tech hat. [00:53:11] [2/2] Or maybe I make a wiki on beta for now and populate it. Once we decide on whether it's useful we can import its content into a prod wiki. [00:53:22] at the time I did also check the update.php hooks for all extensions with patches and there wasn't anything to add [00:53:31] Imo it will making the extension testing process a lot smoother because you can just use some js to mark an extension tested by clicking a button. [00:53:54] yeah I hate Phorge for editing [00:54:23] it's so annoying how when you change one thing on the task, the diff viewer shows the entire text rather than just what changed [00:54:34] Ok maybe we just create a wiki on prod then. Don't want to abuse my tech hat to bypass the wiki creation process though. [00:55:25] It actually works better on an email notification so I just look at that lol [00:56:49] https://extensions.mirabeta.org/wiki/Main_Page ok I will populate this beta wiki for now [00:56:50] I mean when I made bucket wiki the AI just auto-approved it anyway [00:57:38] Oh I only submitted 3 wiki requests. Yeah should be fine I guess. [00:58:00] but this is for actual tech coordination so A) the AI would probably end up approving it and B) yeah you absolutely could use tech account [01:07:52] There often is. SQL done in the prior upgrade and maint script to populate the data the next time. [01:09:12] ah ok that's lovely and intuitive [01:09:21] When was this wiki created? Recently? If so I may need to run upgrade on it again as I just switched over new wikis like 5 minutes ago. [01:10:06] although in that case there should really be a new `LoggedUpdateMaintenance` script too. then again can't trust all extension makers to make sense [01:10:58] Not always such as OATHAuth:UpdateKeysToLatestVersion which now needs ran every single upgrade also. [01:12:18] I guess MediaWiki development is never boring huh [01:13:35] Nope lol [01:13:56] Ran SQL and scripts for extensionswikibeta now btw. [01:15:44] Yes we need to figure this out and what that URLShortner one does still. After that, we should be ready to go for full extension testing, and in about a week move onto NextTide if we get the most important extensions tested by then. [01:16:44] Ah thanks! Was setting it up. [01:17:05] All new wikis on beta will automatically use 1.47 also. [01:31:54] No problem. Also seems the legacy thing for URLShortner is only needed if we enable `$wgUrlShortenerLegacyTemplate` which was added for comparability with the old ShortUrl extension which was now sunset. We never used it so we have no reason to enable it and thus don't ever need that I don't think. [01:32:42] https://phabricator.wikimedia.org/T107188 [01:33:38] This reminds me that we should probably give local wikis the option between using a central database or a local wiki one for short URLs. I think Vocaloid Lyrics Wiki likes their old scheme better. [01:36:19] We can do that but after 1.47. I want to put our focus on 1.47 first then we can do that as a priority after post upgrade maintenance is done. [01:45:05] @posix_memalign https://github.com/miraheze/mw-config/pull/6632 [02:57:40] [1/2] upv2 centralauth related checkbox fields becomes input [02:57:40] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1569184166602604708/image.png?ex=6af28823&is=6af136a3&hm=6203694b39466a2ea2e9ba2a5ffa35ea662a6abea44be260b5784b0df402b94b& [02:59:58] [1/2] seems oa linted it wrong (wait this is manually done? [02:59:58] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1569184747991601262/image.png?ex=6af288ad&is=6af1372d&hm=63d42a3e81e4fd83d1ee42062a8b98734c00d096684ccd6ac31543a64d445a81& [03:03:15] https://gitlab.com/telepedia/extensions/userprofilev2/-/merge_requests/21 [04:03:35] [1/2] @jenny_on_wiki Any thoughts on https://extensions.mirabeta.org/wiki/List_of_extensions ? [04:03:35] [2/2] A lot of it is written by AI but I just want a functioning prototype ahead of extension testing. We will need to clean up the Lua module but I think the current interface is a lot better than before. [04:05:37] status can be a dropdown [04:14:07] Yeah I intend to improve the usability of https://dev.miraheze.org/wiki/JsonEditor but for now we'll keep it minimal [04:21:29] oh it's reuse of that [04:23:18] how does it avoid edit conflict btw? [04:35:55] There is no mechanism for that lol [04:36:31] I guess it can refetch the page before saving which rules out 99% of cases of edit conflicts [04:58:14] [1/2] oh there is one [04:58:14] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1569214511926222990/image.png?ex=6af2a466&is=6af152e6&hm=288cd978384cc061de21f3af32875afe739e0deafadd9f86d3ee11ab4a21b6a9& [04:58:39] so it rejects as long as page is edited after opening the editor [04:59:05] [1/2] Is it apparently super hard to review things on gitlab... [04:59:06] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1569214726896877618/Screenshot_20261108_215842_Chrome.png?ex=6af2a499&is=6af15319&hm=2f1ae76c34d9a11ed766da3e2eb3d88c3bb8b5c7decbcf517a8afdd95918c11d& [04:59:35] they want you to login to bypass the limit [05:00:50] I dont remember my login for gitlab lol [05:01:53] yes this would be better; this merges edits with no conflict automatically and is also how mine is implemented https://xyy.miraheze.org/?oldid=120059#L-410 [05:02:21] @originalauthority do you have a way to report security issues on gitlab or do you want me to just DM you? [05:04:21] i think they use jira for telepedia extensions? not sure [05:04:26] I got the same thing [05:04:31] [1/2] I saw that too when looking at UPV2 diffs. [05:04:32] [2/2] Took me 3 or 4 diffs before getting ratelimited, but I switched to a different browser later. I think my combination of UAs (Linux + Chrome 151) is rare enough but frequently abused. [05:04:32] Yes [05:04:56] i often met this when i didn't login [05:04:58] I got rated on windows using zen [05:08:37] [1/2] oh i remember now. i did make an account for it before but they don't allow me [05:08:38] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1569217124830814208/image.png?ex=6af2a6d5&is=6af15555&hm=5216e60749c773d7cefa332d1e4b5e76bebc633a6684f44bff0006bad2c24fc2& [05:10:08] maybe https://telepedia.atlassian.net/servicedesk/customer/portal/1/group/1/create/4 is the correct place? the link from gitlab doesn't work [08:02:54] Yeah it took me like 25 minutes lol [08:04:05] Yeah I started moving off because of this it's horrific now [08:04:27] You can just DM me [08:35:52] Who is Conscience93? [08:36:50] Elisa [08:37:54] Ahhh. [08:52:18] Yes it is my very very old name way back. Too lazy to change it :xsob: [08:56:13] Fair enough lol. [08:56:24] Has cache cleared for you with ManageWiki yet? [08:57:08] yes the settings works. You can see it from here https://exttest.mirabeta.org/wiki/Special:ContributionScores [08:57:23] I, uh, exclude my ownself lmao [08:58:51] Maybe my cache still needs to clear, I only see the bot setting. [11:12:18] Just doing a bump to see what's the ETA with the ManageWiki update [11:29:41] I think it's already feasible? There is an existing example that runs a maintenance script (e.g. https://github.com/miraheze/mw-config/blob/7f4f662c276d62fe721247748e6e74d7f8382016/ManageWikiSettings.php#L1502). [11:30:12] I guess you can just submit a PR and ask @elisapoly to test it on beta. If it works then you are all good. If not we can see what we need to change. [11:31:23] It's not [11:31:56] While you can run maintenance scripts when a setting is changed, you can't run it when a specific value is set. [11:32:33] I can add support in ManageWiki after 1.47 which is our current focus though. [11:33:25] It's harmless to run the script when the option is enabled I think? [11:33:55] It'll likely clear empty values which is basically a no-op [11:34:06] It shouldn't be ran when it's not needed unless real name is added to hiddenprefs, which we also have to make clear what if will do as otherwise it's accidental data loss. [11:34:50] If real name is not added to hidden prefs then we can't run the script or Everytime it's changed in any way it would get removed regardless of if it's hidden. [11:35:07] There is no way for it to know it's enabled currently [11:35:59] 🤔 I wonder if it'd be better to run the "clear real names" maint script for now [11:36:07] Also I need to make real name selectable in hidden prefs but wont do that until we can make script work properly otherwise it gets hidden but can't be cleared. [11:36:18] Would be a good chance to see how ithe script performs on a real wiki [11:36:57] Not entirely sure what you mean? We don't want it cleared until real names is selectable in hidden prefs otherwise they just add it back? [11:37:38] And conversely we don't want to make it possible to select real name there until we can make doing so automatically run the script so that real name isn't stuck with no way to manually clear as well. [11:38:02] Oh sorry I meant running the maint script to prevent infoleak since VLW isn't getting real name hidden in the near timeframe [11:38:55] It can be a standalone wmg variable which makes things a lot more clear than one of many options in hidden pref [11:39:06] For context VLW edited the MediaWiki i18n message for setting real name to really discourage setting real name but we haven't really asked people to remove their real names [11:40:13] I don't think that should be what we should do, it complicates it and makes it more confusing what it is actually doing as MediaWiki docs would conflict with what it truly does. [11:40:35] I don't think it makes things more clear, I think it makes it more confusing personally. [11:41:17] [1/2] It would work similarly with `wmgCodeMirrorEnableDefault` which we already use [11:41:17] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1569315940900802590/image.png?ex=6af302dc&is=6af1b15c&hm=9afc2a5fd933f1b10122c6ce31e69a7197dda0dc3734b3cfe8339f55483f6c11& [11:41:39] Granted we don't make `wgDefaultUserOptions` configurable by itself [11:41:51] That's different because of that yeah. [11:42:13] By making hiddenprefs itself available I feel we should stick to letting it be manageable there. [11:43:45] I want to reduce how much variables we have in ManageWiki and adding more just adds to the bloat. Eventually it will be less of a concern when I do the redesign of it though. [11:43:50] this looks nice [11:45:19] Do I have the okay to file a Phorge task on this? [11:45:47] Yes we can run the script for you now but that won't stop people adding it back for now. [11:46:36] Also... I wonder how it will behave if they have real name set via Global Preferences? [11:46:54] It's fine. I did say here that we've changed the disclosure on Special:Preferences to be clearer in that we don't want people to enter their real names [11:47:32] Feel free to file task then [11:47:55] can someone help me [11:48:19] I am going to go sleep here shortly, so won't be doing it myself tonight though. [11:48:25] With what? [11:49:48] [1/2] im trying to uploading my files but it says disabled [11:49:48] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1569318082915082260/Screenshot_2026_1109_192702.jpg?ex=6af304db&is=6af1b35b&hm=fa254fe722f9b6af9379aefb5a28e64ab5ff7f2a9af635cb1d450e238ee1caa4& [11:50:28] [1/2] https://issue-tracker.miraheze.org/maniphest/task/edit/form/3/ [11:50:29] [2/2] This form doesn't seem to actually do anything different to the basic form? [14:03:54] the field is not present in globalpref [14:04:09] iirc [14:22:15] Interesting problem, I rolledback an image revision on this file: https://portalmod.miraheze.org/wiki/File:Background.png, however the cache hasn't been purged or the image hasn't been reverted within swift? https://static.wikitide.net/portalmodwiki/2/26/Background.png [14:22:39] Cache is a weird thing. [17:31:40] is there somewhere I can post this request where it won't get buried/lost? [17:47:36] :DoneMH: [17:48:13] Just be annoying as we are terrible at checking that queue in future [17:48:22] I get it :) thank you!