Page MenuHomePhabricator

Abusefilter claims it has disabled itself but is still on and filtering (wgAbuseFilterEmergencyDisable broken?)
Closed, DuplicatePublic

Description

Original task title: Abusefilter claims it has disabled itself but is still on and filtering (wgAbuseFilterEmergencyDisable broken?)

https://commons.wikimedia.org/wiki/Special:AbuseFilter/137

Flags:
Warning: This filter was automatically disabled as a safety measure. It reached the limit of matching more than 5.00% of actions.
☑ Enable this filter

but according to its abuse log, it's still filtering and the check mark at "Enable this filter" is still set and it wasn't changed since Jan 06.

Bildschirmfoto_am_2015-01-22_um_20.12.55.png (1×1 px, 79 KB)

Event Timeline

Rillke raised the priority of this task from to Needs Triage.
Rillke updated the task description. (Show Details)
Rillke added a project: AbuseFilter.
Rillke subscribed.

If I recall correctly, the "Enable this filter" check mark vanished from auto-deactivated filters.

Rillke set Security to None.

Is it really an "emergency" if the filter spikes above 5% for a short while?

Is it really an "emergency" if the filter spikes above 5% for a short while?

This is tweakable. Ewp has, for example, adjusted the value for [[ http://noc.wikimedia.org/conf/highlight.php?file=InitialiseSettings.php | wmgAbuseFilterEmergencyDisableCount to 25 ]].