121848 - generate "potential duplicate" warning on twice-submitted form

Status: RESOLVED DUPLICATE of bug 42946

(Bugzilla :: Email Notifications, enhancement, P1)

Description

[Myk Melez [:myk] [@mykmelez]]

This happened recently:

Subject: [Bug 99691] nsBoxToBlockAdaptor should not be creating a space manager
From: [e-mail]
Date: Thu, 24 Jan 2002 10:59:17 -0800 (PST)
To: [e-mail]

http://bugzilla.mozilla.org/show_bug.cgi?id=99691

[e-mail] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #66221 [details] [diff]|                            |has-review
             Status|                            |



------- Additional Comments From [e-mail] 2002-01-24 10:59 -------
(From update of attachment 66221 [details] [diff] [review])
r=dbaron, although I wonder whether you want NS_NewBlockFrame or
NS_NewAreaFrame.


------- Additional Comments From [e-mail] 2002-01-24 10:59 -------
(From update of attachment 66221 [details] [diff] [review])
r=dbaron, although I wonder whether you want NS_NewBlockFrame or
NS_NewAreaFrame.

Comment 1

[Jacob Steenhagen]

I don't think this is processmail's fault.  If you look at bug 99691, comment 8
and 9 are identical to eachother and what's shown in the e-mail.  I am really
curious how this happened, though.

Comment 2

[Dave Miller [:justdave]]

pretty simple actually...

dbaron accidently hit his submit button twice.

both processes ran nearly simultaneously on the server...

a) process_bug.cgi fires and enters comment 8, then runs processmail on the bug.
b) process_bug.cgi fires and enters comment 9, then runs processmail on the bug.
c) processmail gets control from step a, and finds both comments already in the
bug, so does its duty and reports them.
d) processmail gets control from step b, finds nothing on the bug worth
reporting (it was already reported by the process running in step c) and doesn't
mail anything.

Comment 3

[Jacob Steenhagen]

And because step d) didn't create a mid-air collision, the processing code
didn't think there was anything abnormal about it...  makes sence to me.

Comment 4

[Myk Melez [:myk] [@mykmelez]]

Duh, I should have looked at the original bug.  So, Bugzilla is doing the
half-right thing.  The most-right thing would be to warn the user they might be
submitting a duplicate change when they submit the same form twice.  Changing
the summary to reflect this change and reducing severity to enhancement.

Comment 5

[Dave Miller [:justdave]]

Changing default owner of Email Notifications component to JayPee, a.k.a.
J. Paul Reed ([e-mail]).  Jake will be offline for a few months.

Comment 6

[Dave Miller [:justdave]]

*** This bug has been marked as a duplicate of 42946 ***

Comment 7

[Dave Miller [:justdave]]

clearing milestone on all DUPLICATE/WONTFIX/WORKSFORME/INVALID so they'll show
up as untriaged if they get reopened.  "Jiminy Cricket!" for the filters (and I
don't care if it's spelled wrong ;)