Last modified: 2014-05-14 08:28:48 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 T66583, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 64583 - Flow abuse filter hits not being logged
Flow abuse filter hits not being logged
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-29 03:25 UTC by Jasper Deng
Modified: 2014-05-14 08:28 UTC (History)
6 users (show)

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


Attachments

Description Jasper Deng 2014-04-29 03:25:35 UTC
As of 3:24 UTC, https://www.mediawiki.org/wiki/Special:AbuseFilter/28 showed "Of the last 144 actions, this filter has matched 4 (2.78%).", but the hits were not logged. Either that line was wrong or, as I suspect, the filter hits are not being logged.
Comment 1 Kunal Mehta (Legoktm) 2014-04-29 07:02:28 UTC
I peeked in the database, and didn't see any log entries for that filter.

Flow calls \AbuseFilter::filterAction which in turn calls self::addLogEntries.  Still investigating.
Comment 2 Kunal Mehta (Legoktm) 2014-04-29 07:16:15 UTC
I can't reproduce this locally, logging is working fine.
Comment 3 Jasper Deng 2014-04-30 07:33:04 UTC
This might have something to do with spamblacklist, as the entries added in https://www.mediawiki.org/w/index.php?title=MediaWiki%3ASpam-blacklist&diff=984908&oldid=961892 target this spambot. Possibly spamblacklist is the one actually blocking it, but then doing something funny (it also doesn't log its (apparent) flow hits in https://www.mediawiki.org/wiki/Special:Log/spamblacklist).
Comment 4 Jasper Deng 2014-05-14 06:55:44 UTC
Now it shows 2 hits, which still doesn't answer the question of why, as of 7:55 UTC, it shows "Of the last 172 actions, this filter has matched 44 (25.58%). On average, its run time is 36.91 ms, and it consumes 70 conditions of the condition limit." Maybe it has something to do with caching?

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


Navigation
Links