emitting Ultraviolet light, 24/7
User Details
- User Since
- Sep 26 2020, 10:03 AM (290 w, 23 h)
- Availability
- Available
- IRC Nick
- sportzpikachu
- LDAP User
- Sportzpikachu
- MediaWiki User
- Sportzpikachu [ Global Accounts ]
Thu, Apr 2
(sort of) reproducible with Firefox dev tools:
Yes, that's right, thanks very much! I can see the token in the CI settings. Most likely we will start working on the integration test MVP after Easter.
Mon, Mar 30
Wondering if any announcement was made/could have been made of this earlier? It's quite confusing to get a change suddenly abandoned after 2+ years of no activity with no reason attached. A quick search of my inbox shows that this task wasn't mentioned in any of the lists I'm subscribed to, nor was it announced in Tech News.
Wed, Mar 25
Do you need any other accounts?
Mon, Mar 23
See also T206406: Main Page on a wiki doesn't have a Discussion page / Talk page on Mobile View in which the Talk button was added for logged-in users (but not for anons) on [[Main Page]].
Mar 19 2026
We need to get you a token. The token is limited to 3 environments at a time (meaning three separate MediaWikis for tests at the same time)—is that sufficient?
3 environments should be plenty - we won't need the environments to be kept up, they will (hopefully) be destroyed right after each test run.
Fixed in Special:Diff/1344276697. Thanks for reporting!
Mar 18 2026
Mar 16 2026
I do a lot of recent change patrolling, and find that I use "No reliable source" and "Test edits" very frequently, so I would like them to be on the main toolbar for reverting edits. Not everyone will necessarily need the same options as frequently, so it would be good for it to be configurable so that people can adjust to their needs.
The UV preferences page already has a similar feature for the UI elements displayed in the top-right of a page. This would be exactly like that: a checklist with some default options, and it would be in the "Revert" section. This allows users to configure reverting options in accordance with the actions they most often use.
Mar 12 2026
Thanks for your response! Right now we just deploy through action API+REST API with a CD script (which has an approval flow that we could skip for the CI test probably), since UV is just a normal userscript page onwiki. We won't deploy any extensions - however it would be nice to have the extensions that are on enwiki so that we can test features such as CheckUser, pending changes, etc. I don't think we would need a chart update for this - normal working MW instance would probably be good enough.
Mar 6 2026
Feb 13 2026
Feb 7 2026
Implemented on vue
Nov 25 2025
Jul 28 2025
Jul 7 2025
Although there is a point that section title layout is not strictly language-based but by local wiki convention - hence it could be in local config instead of i18n.
This is currently handled with a helper function (src/util/getMonthHeader.ts).
Jun 2 2025
Not at all, thanks!
May 31 2025
Merged in a09cb65d, deployed in Special:Diff/1293199845
May 28 2025
Trying to follow https://www.mediawiki.org/wiki/GitLab/Workflows/Security_patches but step 2 needs me to create a new group. I can't seem to find this button (I probably don't have the permissions to do so)
Fully protected for now. https://en.wikipedia.org/w/index.php?title=Special:Log&logid=170067682
May 12 2025
May 11 2025
May 10 2025
May 6 2025
Hi @Iniquity, apologies for the late response. Unfortunately at the moment localisation of Ultraviolet is not available. However it is planned and definitely a priority for the rewrite.
Jun 18 2024
I encountered the same problem with Gitlab not letting me delete the custom issue tracker on repos/10nm/ultraviolet. Generated a new access token for the project (/-/settings/access_tokens) then used the Disable a custom issue tracker API route to delete the custom issue tracker:
Jun 15 2024
Jun 7 2024
Bitu is showing the old email again, and triggering an email change caused Bitu to send an email Someone, hopefully you, has requested that your email address for your Wikimedia Developer Account (sportz) be updated from wiki@sportshead.dev to wiki@sportshead.dev. To confirm this change please click here:. The new email is definitely being stored somewhere, just not in the right place
@taavi: logged out and logged back in but MediaWiki doesn't seem to have updated the email. Special:Preferences is still showing the old one.
Seems like Bitu actually saves the new email somewhere, but doesn't actually change it for wikitech. I changed from sportzpikachu@gmail.com to wiki@sportshead.dev on 2024-05-09, and I thought it had worked but just now I noticed that wikitech still had my old email, and I clicked the link to https://idm.wikimedia.org/accounts/email/ (which should probably show the current email) from the wikitech preferences page. Changing the email again causes Bitu to send a new email Someone, hopefully you, has requested that your email address for your Wikimedia Developer Account (sportz) be updated from wiki@sportshead.dev to wiki@sportshead.dev. To confirm this change please click here: <link>, clicking the link changes it in the Bitu dashboard but not in wikitech. I'll keep checking the Bitu dashboard to see if it reverts at any point
Jun 6 2024
Thanks for the bug report! At the moment, Ultraviolet doesn't support mobile devices. However, we will add an option (like in RedWarn) to move the page icons to a dropdown menu with plain links instead, which should solve (or at least reduce the impact of) this issue.
Fixed on vue branch (T348406) in b62f875 feat: preferences page, setting components
Jun 4 2024
May 24 2024
May 23 2024
Fixed in 74fbb05. Gitlab Job #267229
May 22 2024
A git-bisect shows that this was broken starting in rMW610b9ac91c4b: jquery.makeCollapsible: Make toggle buttons work inside cloned content (T362561), where the behaviour of jquery.makeCollapsible was changed. The patch causes jquery.makeCollapsible to expect the toggle link to be inside the collapsible details, whereas ApiSandbox puts the toggle link wrapper and collapsible details as siblings:
May 17 2024
May 9 2024
Reproduce:
- Add P62264 to your common.js
- Create a test page with <div id="app"></div>
- Load the test page with ?debug=2 to load the dev version of pinia
- Use the counter and observe the state updating correctly
- Use the "Trigger HMR" button to simulate a hot module reload
- Observe the error in the console
May 8 2024
May 6 2024
Some problems with mw.Message and its Vue plugin:
- Doesn't seem to have bidi support by default (provided by mw.jqueryMsg module)
- No locale key loading - no fallbacks, etc
- only way to switch locale is by overriding keys
- No reactivity with message keys
- Keys must be loaded before any UI is mounted (i.e., configuration must be loaded and user-defined locale must be loaded before UI mount)
- Locale switching does not affect UI and requires a reload
Apr 29 2024
Apr 26 2024
Mar 1 2024
Feb 9 2024
Dec 3 2023
Nov 21 2023
Fixed in Special:Diff/1186232485.
