Last modified: 2013-04-12 18:41:45 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 T38684, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36684 - Spammy failed to merge messages
Spammy failed to merge messages
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: upstream
: 44007 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-09 05:32 UTC by Niklas Laxström
Modified: 2013-04-12 18:41 UTC (History)
6 users (show)

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


Attachments

Description Niklas Laxström 2012-05-09 05:32:55 UTC
Apparently Gerrit sends a failure message every time it tries to merge a patch which has missing dependency. This can make tens of messages per day. Fortunately they do get into the same thread, so one can just skip over them easily.
Comment 1 Chad H. 2012-05-09 17:13:54 UTC
I'm not sure how this is a bug. What is the desired behavior?
Comment 2 Niklas Laxström 2012-05-09 17:26:23 UTC
Perhaps restrict the emails only to submitter and author and not all reviewers?
Comment 3 Chad H. 2012-05-15 13:46:45 UTC
There's actually a discussion going on currently on the upstream list, repo-discuss. I've taken the time to weigh in.

In an ideal world, I think users should be able to customize what sorts of e-mails they get.
Comment 4 Chad H. 2013-01-15 18:36:00 UTC
*** Bug 44007 has been marked as a duplicate of this bug. ***
Comment 5 Matthew Flaschen 2013-01-15 19:00:20 UTC
Chad, the ideal behavior is that it not send the latter emails at all, since nothing has changed.

If the dependency gets merged, then obviously it should do the merge.  But I can't see why anyone would want useless emails that said "The same thing I tried before failed again, since the situation has not changed".
Comment 6 Matthew Flaschen 2013-01-15 19:01:01 UTC
It probably shouldn't even keep commenting on the site itself, for the same reason.
Comment 7 Chad H. 2013-01-15 19:20:21 UTC
It's not supposed to repeat comments that are identical, but the logic's been a bit broken for some time. After we upgrade, I'm thinking of disabling the behavior (or at least set it to a much longer interval) until it's fixed to not spam people.

The spam is the same (comments & e-mail), and should be treated as one issue (hence the dupe).
Comment 8 Chad H. 2013-04-12 16:31:08 UTC
Have we had this problem recently?
Comment 9 Matthew Flaschen 2013-04-12 18:17:13 UTC
I haven't.
Comment 10 Chad H. 2013-04-12 18:40:47 UTC
I'm going to tentatively mark this fixed. If anyone sees it, please reopen and we'll look at it again.

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


Navigation
Links