User Details
- User Since
- Oct 7 2014, 2:31 PM (409 w, 6 d)
- Availability
- Available
- LDAP User
- Umherirrender
- MediaWiki User
- Umherirrender [ Global Accounts ]
Yesterday
I have downloaded refs/changes/62/808262/29 and it works for me (on mariadb/mysql)
SELECT cuc_namespace,cuc_title,cuc_user,cuc_user_text,cuc_comment,cuc_actiontext,cuc_timestamp,cuc_minor,cuc_page_id,cuc_type,cuc_this_oldid,cuc_last_oldid,cuc_ip,cuc_xff,cuc_agent FROM `cu_changes` FORCE INDEX (cuc_ip_hex_time) JOIN `user` ON ((cuc_user=user_id)) WHERE cuc_ip_hex = 'v6-00000000000000000000000000000001' AND (cuc_user != 0) AND ((user_editcount < 500) OR (user_registration > '20220716210205')) ORDER BY cuc_timestamp DESC LIMIT 5001
MariaDB [cswiki_p]> select max(af_id) from abuse_filter; +------------+ | max(af_id) | +------------+ | 138 | +------------+ 1 row in set (0.002 sec)
Have found the corresponding bug for your "feature" request: T274618: Return actual integers when selecting integer fields from the DB
All returns from the database are strings. If the database does not convert a wrongly given default, that sounds like a bug there. Mysql has accept the default, because it can cast the string 0 to a numeric 0.
The mediawiki database layer returns everything as string, even it is integer in the database.
Sounds similiar to T253489#6163546, just say for which table the index is
Sat, Aug 13
It now passed on the the patch https://gerrit.wikimedia.org/r/c/mediawiki/core/+/822708 from today
FAILURE: https://integration.wikimedia.org/ci/job/mediawiki-quibble-composer-mysql-php80-docker/407/consoleFull
PASS: https://integration.wikimedia.org/ci/job/mediawiki-quibble-composer-mysql-php80-docker/408/consoleFull
I have also seen the segfault on https://gerrit.wikimedia.org/r/c/mediawiki/core/+/816261, but assumed it was for the changed tests, not flaky.
Fri, Aug 12
Tue, Aug 9
The inserted options rcenhancedfilters-seen-tour and wlenhancedfilters-seen-tour are set in LocalUserCreated hook (from the WikimediaMessages extensions, but there are more extensions as well).
Mon, Aug 8
The best support for mysql is to remove the EXISTS check. It seems only exists on DROP TABLE, but not on other DDL statements
Sun, Aug 7
UNIQUE INDEX cx_translation_ref ( translation_source_title, translation_source_language, translation_target_language, translation_started_by ),
The refered unique index contains a user id, so this could be a double-click or something which is trying to store the same thing twice over the api (ApiContentTranslationSave)
The log message cannot longer happen since https://gerrit.wikimedia.org/r/c/mediawiki/core/+/758592, because Timeouts are rethrown and not logged anymore
Sat, Aug 6
The backlog for that template is now processed after a fresh recursive link update has been started via api's action=purge
The job queue is designed to do the reparses, because that does not fit into one only transaction, wikitext processing is expensive.
Sounds like a sub task of T304979 or at least related
The index get dropped with T314041
Fri, Aug 5
The deletion of templatelinks is done via the job queue, because reparsing many pages takes some time. The counts are at 0 now.
Flow produce its own recent changes line and set the type RC_FLOW to 142, that is what you are seeing. As the core types are known there are mapped to the string values (via RecentChange::parseFromRCType), but flow is not known there.
Thu, Aug 4
Without further parameter on the request url it is hard to tell which api module is affected, but this is commons and long transactions on upload was improved with https://gerrit.wikimedia.org/r/c/mediawiki/core/+/735762 (part of T283045)
addWiki.php is documented to get run on another wiki, while creating a new wiki and this is the addition of the main page to the new wiki (https://guw.wikipedia.org/w/index.php?oldid=1&uselang=en matched also this bug creation timestamp)
$wgUser was already removed with T242679, $wgTitle and $wgOut still there
Wed, Aug 3
There are also some unneeded deletion on the preferences, which could hold locks as well, see T301506
Tue, Aug 2
@DBA, @Performance Team:
Mon, Aug 1
I fixed that indirectly with a replacement in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/UserMerge/+/759828 which is in 1.38
Sun, Jul 31
$wgAbuseFilterNotifications = 'rc' or 'rcandudp' is broken as well and throws CannotCreateActorException (it's post send, not visible to the wiki), the proposal does not fix that part (because CheckUser would be called from RecentChanges for that configs)
Sat, Jul 30
Fri, Jul 29
First collection with the abstract schema file names (as of now) and some dblist entries
The equivset is to handle "Visually similar characters". The persian digits are semantical identical and mediawiki already supports that with $digitTransformTable in the language file.
There is already another mapping for that character
Thu, Jul 28
The database field spoofuser.su_name should be made binary to be equal to the field user.user_name and behaviour correctly when the database collation not defaults to binary
Just as note to avoid confusing: The fix only applied to new log entries after the deployment, because the changed code is used on store into check user, not on read of the stored data
A deprecation notice should not break your wiki, the message may be shown and it looks broken.
There is a setting named for that: https://www.mediawiki.org/wiki/Manual:$wgExtraGenderNamespaces