Page MenuHomePhabricator

$wgAbuseFilterEmergencyDisableThreshold is ignored
Closed, InvalidPublic

Description

A filter matching more than 6% of the edits is still active even if the the default value for $wgAbuseFilterEmergencyDisableThreshold is 5%:
https://pt.wikipedia.org/wiki/Special:AbuseFilter/180?uselang=en
"Of the last 4,559 actions, this filter has matched 297 (6.51%). On average, its run time is 0.22 ms, and it consumes 4.9 conditions of the condition limit."

Event Timeline

He7d3r created this task.Oct 5 2020, 2:24 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 5 2020, 2:24 PM

As per https://www.mediawiki.org/wiki/Extension:AbuseFilter#anchor-Emergency_throttling, even if a filter is throttled, so-called "safe" actions are still allowed (and I assume that safe actions means those not in $wgAbuseFilterRestrictions (e.g. block, rangeblock, blockautopromote, degroup) so warn, disallow, tag, etc. would, in theory, still work (ping @Daimona who knows better).

Thanks, I had already seen this (as as I get notifications for all AbuseFilter tasks). Actions are ininfluent here, the filter should be throttled all the same (even if it has no impact). I think this might just be some caching issue/edge case, but will investigate later.

Daimona closed this task as Invalid.Oct 5 2020, 3:07 PM

There you go, the stats were reset and the filter was throttled. Likely some caching issue. T264629 could help, probably.

He7d3r added a comment.EditedOct 5 2020, 5:54 PM

There you go, the stats were reset and the filter was throttled. Likely some caching issue. T264629 could help, probably.

Indeed, now the main page says it is "Enabled, throttled":
https://pt.wikipedia.org/wiki/Special:AbuseFilter?offset=179&limit=1&uselang=en