User Details
- User Since
- Dec 12 2020, 11:36 AM (81 w, 58 m)
- Availability
- Available
- IRC Nick
- zabe
- LDAP User
- Zabe
- MediaWiki User
- Zabe [ Global Accounts ]
Thu, Jun 30
[e63a6c70-26b5-4b1f-b807-3f39c105554d] /wiki/Special:RecentChanges?hidebots=1&translations=filter&hidecategorization=1&hideWikibase=1&limit=50&days=7&urlversion=2 Wikimedia\Rdbms\DBQueryTimeoutError: A database query timeout has occurred. Query: SET STATEMENT max_statement_time=30 FOR SELECT rc_id,rc_timestamp,rc_namespace,rc_title,rc_minor,rc_bot,rc_new,rc_cur_id,rc_this_oldid,rc_last_oldid,rc_type,rc_source,rc_patrolled,rc_ip,rc_old_len,rc_new_len,rc_deleted,rc_logid,rc_log_type,rc_log_action,rc_params,rc_actor,recentchanges_actor.actor_user AS `rc_user`,recentchanges_actor.actor_name AS `rc_user_text`,comment_rc_comment.comment_text AS `rc_comment_text`,comment_rc_comment.comment_data AS `rc_comment_data`,comment_rc_comment.comment_id AS `rc_comment_cid`,rc_title,rc_namespace,page_latest,(SELECT GROUP_CONCAT(ctd_name SEPARATOR ',') FROM `change_tag` JOIN `change_tag_def` ON ((ct_tag_id=ctd_id)) WHERE ct_rc_id=rc_id ) AS `ts_tags` FROM `recentchanges` STRAIGHT_JOIN `actor` `recentchanges_actor` ON ((actor_id=rc_actor)) JOIN `comment` `comment_rc_comment` ON ((comment_rc_comment.comment_id = rc_comment_id)) LEFT JOIN `page` ON ((rc_cur_id=page_id)) WHERE rc_bot = 0 AND (rc_type != 6) AND (rc_source != 'wb') AND (rc_namespace NOT IN (1198,1199,866,867)) AND (rc_timestamp >= '20220623210517') AND rc_new IN (0,1) ORDER BY rc_timestamp DESC LIMIT 50 Function: SpecialRecentChanges::doMainQuery Error: 1969 Query execution was interrupted (max_statement_time exceeded)
Wed, Jun 29
Also see T304482.
Tue, Jun 28
Na, that's not the new column.
We had more than a million of these in the last hour.
Mon, Jun 27
Sun, Jun 26
Sat, Jun 25
Support. I would also like to point out that this gerrit -1 query is not very meaningful, as it only shows the patches that currently have a -1 from Dreamy, but not the ones he gave -1's to in the past.
Tue, Jun 21
It seems like nothing is left to do here.
Sat, Jun 18
I see no task associated with it and no discussion about it.
Thu, Jun 16
Btw. members of wmf-supportsafety are already capable of doing this due to them having userrights-interwiki, is that not sufficient?
This doesn't sound good to me. While testwiki is there for testing purposes, there are valid suppressions happening there, e.g. due to users accidentally editing while being logged-out.
Mon, Jun 13
But OutputPage::setPageTitle() calls Sanitizer::removeSomeTags, is that not enough?
Sun, Jun 12
Sat, Jun 11
Fri, Jun 10
Thu, Jun 9
Tue, Jun 7
I guess you mixed up the patch number, 803371 is a core patch.
Could you (or someone else) add me to that task?
Mon, Jun 6
Sun, Jun 5
Thu, Jun 2
There is a deeper problem with AbuseFilter sending data related to non-existent users to CheckUser (see T188180#7975147). CheckUser actor migration is basically stalled on fixing this. Let's stop writing to cuc_actor completly for now until we have a solution for that.
@Dsharpe could I get access to T280413?
Jun 1 2022
abuse_filter_log saves non-existing users when AbuseFilter prevents account creation. This now make problems with the actor migration in checkuser, see T309737. Any ideas what we should do about that? It also basically makes actor migration for that table impossible in the current situation.
May 29 2022
LiquidThread still selects that column, now causing fatals: T309460.
May 28 2022
MariaDB [trwiki_p]> select * from page limit 1; ERROR 1356 (HY000): View 'trwiki_p.page' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them MariaDB [trwiki_p]>
May 27 2022
FTR, it seems like beta-update-databases-eqiad was running out of memory while trying to perform the migration added in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikiLambda/+/798987. I manually ran the migration script (sal), hopefully that fixed it.
The error showed up at enwiki, where we are not yet writing to cuc_actor (and thus it should also not write to the actor table), thus I can't see how it could be the checkuser changes.
May 25 2022
May 24 2022
~35 instances in the last 15 minutes, tagging as a blocker for now.