User Details
- User Since
- Dec 15 2020, 3:00 PM (118 w, 19 h)
- Availability
- Available
- LDAP User
- Func
- MediaWiki User
- Func86 [ Global Accounts ]
Fri, Mar 3
Fixed by the patch for T306862
Wed, Mar 1
Mon, Feb 27
Fri, Feb 24
Should be resolved with or without the linked patch? It got +2 but the parent change was still pending review.
Note: This works for pre-save transform ({{subst:REVISIONTIMESTAMP:{{subst:PAGENAME}}}}) before commit 5cb4693, because fake revision was not yet set up during PST.
Thu, Feb 23
You should have on-wiki discussions first.
This should be declined.
The Translate extension and other components should try to address the issues you mentioned, not asking translators to translate into multiple variants of Chinese.
@Winston_Sung Please extend the task description. I assume this is for multilingual wikis, am I right?
Tue, Feb 21
Mon, Feb 20
The default message is Intended blockee for a long time, and only have a refactor recently (but the parsed result is the same).
Feb 19 2023
Feb 18 2023
Can you give the use case? I saw the one in Special:Preferences works fine with styles from mw.widgets.TagMultiselectWidget.base.css
Feb 17 2023
That's not how task triaging works.
Feb 13 2023
I finished the import with the patch applied, but I noticed that around 1.15G of memory was consumed by ParserObserver->previousParseStackTraces after around 151000 images were imported.
Feb 12 2023
Feb 11 2023
I want to mention https://github.com/nbdd0121/MW-PinyinSort, not sure which one works better, the patch here or the existing extension.
Feb 1 2023
Jan 31 2023
Seems fixed by refactors, though I found a new bug introduced by refactors, will file a report and submit a patch for it.
Jan 25 2023
Jan 23 2023
I can still reproduce the case I found with Timeless skin and the latest Chrome in my laptop screen size, and I have more information to share now:
In the screenshot below, the 2em of padding was added to .CodeMirror by Timeless. We can see the edge of elements matching the selector .CodeMirror * is uneven, and somehow the position of line breaking was different compared to the edit area.
In the next screenshot, 1em padding was added to the .CodeMirror-lines and .CodeMirror-line elements. We can see now the edge of elements is even and 2019 was attached to the first line as expected.
(maybe this should be filed as another task though)
Noticed this in some build artifacts of test failure when investigating T324879, I thought that was some unexpected state of the CodeMirror since it was not fully loaded/unloaded before typing.
Jan 21 2023
I think the patch should be backported to 1.39, so I cherry-picked it to the v0.44 branch of ooui.
No, this message is only for the database limit, which is fixed to 65530.
Jan 20 2023
Jan 19 2023
So, somehow wikimedia-ui-base.less was not updated in the MediaWiki core for 2 previous OOUI updates?
It was bumped to 20.0 by commit a222a13 which contains the fix (3e13426), and then we have cd023d2 and e1d7d17 in the ooui side, f8a7e46 and fc0acab3 in the core.
What's the process of upgrading ooui in the core? manually? without CI checking?
Jan 18 2023
This is by design.
This parser function would try to use the link cache, if it found matches then return early without increasing the counter or checking again.
You added internal links to each page, then the existence was checked and recorded before processing #ifexist.
Note: The cache would be kept for a while, so if you remove links, would not reflect as too many expensive function calls instantly.
Jan 16 2023
Unpaired escaped quotes would not affect anything.
As you mentioned before, there is only a blank call to mw.user.options.set(), which means nothing to do with js on the client side, but failed to encode json in the backend.
API was designed to give an output when the error is not fatal, so it would normalize the string; while the resourceloader is strict on encoding json.
I reproduced this bug, the problem is how the database truncates the string. I saw a broken Unicode mark at the end of it when retrieving options from API, which means a Chinese character was truncated in half.
Lower the priority since backported.
Jan 15 2023
Jan 14 2023
You can save a copy of your current preferences via Special:ApiSandbox#action=query&format=json&meta=userinfo&formatversion=2&uiprop=options and check if there are any suspicious values.
Jan 13 2023
Too many tasks, these two are nearly identical.
Jan 12 2023
Cool, blank call to mw.user.options.set(), that's interesting. I will try to investigate later today.
The log provided seems not helpful to me, but the description reminds me of T311799. You may try to follow the reproduce steps and my debug suggestion, and share more information here.
The patch is for MoblieFrontend, I think this should not fall into tracking tag.
Sounds like this can solve T302200?
Duplicate of T294716, https://gerrit.wikimedia.org/r/c/mediawiki/core/+/735753.
Similar to T326591.
Jan 7 2023
Jan 4 2023
After studying the log provided in T326071#8493256, I found that the problem is bigger than I thought.
The problematic change would destroy the database when updating from versions before 1.33, though not in the way mentioned in T326071#8493877.
Jan 3 2023
I would like to mention commit 24115a8f4cc0f079f30894bc07eb7476f2dffb3e, it removed the revision_actor_temp table, but the maintenance script was not updated and still try to write to that table rather than the rev_actor field of revision table.
Dec 31 2022
Resolved. 1.37 was EOL, so no backport.
For your second error on 'revision.rev_comment_id', it was fixed in T297031, you should try to use the last release of 1.37 instead.
Dec 24 2022
The rev_user field was removed since 1.35, you may try to use populateUserTable.php provided by the StubUserWikiAuth extension. It supports using the actor table to populate the user table.