Last modified: 2014-02-12 23:38:25 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T23358, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21358 - Filter reacted but it shouldn't
Filter reacted but it shouldn't
Status: REOPENED
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Low major (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-30 12:44 UTC by Lolsimon
Modified: 2014-02-12 23:38 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Lolsimon 2009-10-30 12:44:36 UTC
We have had an edit at nl.wikipedia.org where the filter reacted on. But the filter shouldn't react at that edit. When we test the edit to the filter, it says it doesnt match, but somehow, the filter has reacted at the moment of submit by the editor. The filter has not changed in the time between the edit and now.

We simply don't understand how the filter could react at this edit.

Edit information: http://nl.wikipedia.org/wiki/Speciaal:Misbruikfilter/examine/log/29961
Filter information: http://nl.wikipedia.org/wiki/Speciaal:Misbruikfilter/18
Comment 1 Huib abigor Laurens 2009-10-30 19:53:47 UTC
Fixed. 
Comment 2 Roan Kattouw 2009-10-30 19:55:30 UTC
(In reply to comment #1)
> Fixed. 
> 

Fixed how?
Comment 3 Huib abigor Laurens 2009-10-30 19:56:29 UTC
removing the lcase would do the trick :)
Comment 4 Andre Koopal 2009-10-30 20:31:45 UTC
The bug itself is not fixed. Abigor changed the filter to not use lcase. That solves the problem for this filter, but it seems that lcase is buggy. So please still look into this.
Comment 5 Lolsimon 2009-10-30 20:37:24 UTC
(after editconflict)

No, it isn't fixed at all. The problem isn't in the filter code, that's the problem! 

I'll explain some more;

This is the code of filter that worked:
article_namespace == 0
& article_recent_contributors == ""
& new_size  < 50
& !contains_any(lcase(added_lines),"#redirect","#doorverwijzing")

The edit:
added_lines =  #DOORVERWIJZING[[Eufemisme]]

When I test the full edit at http://nl.wikipedia.org/wiki/Speciaal:Misbruikfilter/examine/log/29961 with the above mentioned filter, it says the filter doesn't match.(!) Somehow the filter /did/ react at the edit, while it wasn't possible. The problem isn't in the filter code, but somewhere else.
Huib changed the code a little bit, but the (old) filter did also work properly.
Comment 6 Lolsimon 2009-10-30 20:50:29 UTC
last sentence of me isn't right, 'Huib changed the code a little bit, but the (old) filter did also work properly', --> 'Huib changed the code a little bit which solved the problem with the filter, but it didn't solve the bug (as mentioned above)'.
Comment 7 Andrew Garrett 2009-11-19 18:47:06 UTC
I can see that the hit should not have occurred, but I have no way of testing or reproducing it, unless somebody can show me a consistent way of reproducing the bug.
Comment 8 Andre Koopal 2009-11-19 20:09:05 UTC
reproducing is hard, as the error doesn't appear always. Given the fix that Abigor did, it seems that the problem is in the lcase-function. But I understand debugging will be hard.
Comment 9 Huib abigor Laurens 2009-11-19 20:26:17 UTC
I will write down what I did so you could reproduce it, I also have the filter code for the moment that the error occurred (before my fix)

But that will be something I do when I have the time, could take a day or two.
Comment 10 Nischay Nahata 2013-03-22 18:39:32 UTC
Any further improvements on this one?
Comment 11 Helder 2013-07-15 19:19:30 UTC
ping.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links