Right now we use a tag to identify such actions, and that is great. However, as we'll have a dedicated AF page to show problematic executions (slow ones and the ones which had a runtime error) it would make more sense to move this info there.
Description
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T209023 Major overhaul for AbuseFilter | |||
| Open | None | T193064 Create a dedicated page for stats | |||
| Resolved | Daimona | T193374 Mass actions always reach condition limit | |||
| Open | None | T193375 Use the problems' dedicated page instead of tags to show actions which hit the condition limit |
Event Timeline
Change 429731 had a related patch set uploaded (by Daimona Eaytoy; owner: Daimona Eaytoy):
[mediawiki/extensions/AbuseFilter@master] Use /problems instead of tagging for actions which hit the conds limit
The tagging was meant not only to help maintainers, but also patrollers. If an edit reaches the limit, no additional checks are executed and a potentionally bad edit might have gone through. Is there any problem with keeping this feature?
@matej_suchanek I didn't think about that. I guess there's no problem in keeping it, I'll just edit the patch so that it won't remove existing code. The real problem here is for mass actions per parent task.
Removing task assignee due to inactivity, as this open task has been assigned to the same person for more than two years (see the emails sent to the task assignee on Oct27 and Nov23). Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome.
(See https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator.)
Change #429731 abandoned by Daimona Eaytoy:
[mediawiki/extensions/AbuseFilter@master] Use /problems together with tagging for actions which hit the conds limit