With an active spam wave, a second report of the same post will raise autoflags.

[makyen]

We had a situation where a bunch of posts were reported for The Workplace troll, but were not autoflagged, because the user got some rep (~40) (sock-puppets?), which put the account above the max rep specified for various detections and the spam waves. I adjusted the rep limits on the detections which were specifically TWP and on the spam waves, which resulted in the user's last post getting deleted and dropping their rep to 1.

No real issue there, other than the rep limits are something which should be examined when not under the gun trying to get them to apply in the heat of the moment.

However, there's an autoflagging issue which should be addressed, which is probably tied in with spam waves. About an hour after the posts were initially reported, an !!/allspam was executed for the user. The reports from the !!/allspam resulted in the posts having autoflags raised on them. In this instance, that was OK, due to the posts not having autoflags raised initially. However, it implies that it may be possible that while a spam wave is active the same post could be reported more than once and have autoflaggs raised each time that the post is reported.

I haven't looked at the code to double check to see if multiple reports will get separately autoflagged. Unfortunately, I probably won't have the time to do so in the next 12 hours.

@Undo1 @ArtOfCode-

[user12986714]

How about add a 'allow flags on vandalism' option for spam wave and do not send autoflags if the option is not enabled and the post has multiple revisions?