The Abuse Filter occasionally stops handling specific edits because it reached the condition limit. It should be possible to see which edits these are - both because they didn't pass the scrutiny of all the filters (and are likely to be problematic), and to allow the Abuse Filter managers to find the expensive filters which cause these.
Description
Description
Details
Details
- Reference
- bz69492
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Tag actions which hit the condition limit | mediawiki/extensions/AbuseFilter | master | +16 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | matej_suchanek | T71492 Edits which hit the condition limit should be tagged | |||
| Open | None | T90754 Allow tracking of max run time / conditions consumed in AbuseFilter |
Event Timeline
Comment Actions
Change 339927 had a related patch set (by Matěj Suchánek) published:
[mediawiki/extensions/AbuseFilter@master] Tag actions which hit the condition limit
Comment Actions
Change 339927 merged by jenkins-bot:
[mediawiki/extensions/AbuseFilter@master] Tag actions which hit the condition limit
Comment Actions
Wow! If you have done what I think you have done, this deserves all the story points and user notices it can get! I'm very much looking forward to seeing this in action!
Comment Actions
What about something like this:
Some edits have to be checked against too many conditions before they can trigger an abuse filter. If any filter is not executed for that reason, the edit will be [{{fullurl:Special:RecentChanges|tagfilter=abusefilter-condition-limit}} tagged] for further review.