Closed
Bug 46741
Opened 25 years ago
Closed 23 years ago
mid-air collision reported when there is no reason to, followed by software error
Categories
(Bugzilla :: Bugzilla-General, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: ekrock, Assigned: justdave)
Details
(Whiteboard: midair)
Using Commercial 2000072508 on WinNT 4.0 SP4.
I'm seeing a suspiciously large number of mid-air collisions reported today by
Bugzilla. And now I have one where there's no evidence that someone else was
really changing the bug at the same time. I see this error message:
Mid-air collision detected! Someone else has made changes to this bug at the
same time you were trying to. The changes made were:
[ and then there are the who what etc. table headers, but no body cells!]
Also, on the Throw away link, I see this text:
Throw away my changes, and go revisit bug 3373233732
Note that bug # is shown twice.
... and when I click to submit anyway, I get this error message:
Content-type: text/html
Software error:
INSERT INTO bugs_activity (bug_id,who,bug_when,fieldid,oldvalue,newvalue) VALUES
(18895,3845,,39,'19608,22254,26508,33732','19608,22254,26508,33732,8388607'):
You have an error in your SQL syntax near
'39,'19608,22254,26508,33732','19608,22254,26508,33732,8388607')' at line 1 at
globals.pl line 134. Please send mail to this site's webmaster for help.
Reporter | ||
Comment 1•25 years ago
|
||
Upping severity to major as data loss occurred because of software error--will
have to retype my comments.
Severity: normal → major
Summary: mid-air collision reported when there is no reason to → mid-air collision reported when there is no reason to, followed by software error
If you modify a bug once and then don't reload before modifying again, it will
look like a midair collision to bugzilla because of the way our cache works
(i.e., differently from 4.x in a way I haven't bother to figure out...). Could
that have happened.
The doubling sounds more serious...
Reporter | ||
Comment 3•25 years ago
|
||
OK, we will keep this bug report to track whatever true Bugzilla issue (e.g. the
software error, the doubling of the bug #s, etc.) that might exist here. I've
opened a separate bug report, bug 46825, to track the Necko cache
incompatibility we seem to have uncovered.
Frankly, I think there's probably no Bugzilla bug here, but two mozilla bugs:
1) bug 46825, which is a cache bug
2) whatever caused the doubling, which is perhaps (this is a guess) a session
history bug relating to hidden form controls. I'll look into it quickly and if
I can come up with something resembling steps to reproduce I'll file it...
Fixing the cache bug might cause the doubling to go away. The doubling could be
something similar to bug 45396...
Assignee | ||
Comment 6•24 years ago
|
||
I was looking for something completely different, and ran across this bug still
sitting in here.
Matty/Dawn: THIS is the source of our mysterious 8388607 showing up in the
database (see the previouss comments).
Updated•24 years ago
|
Target Milestone: --- → Future
Updated•24 years ago
|
Priority: P3 → P2
Target Milestone: Future → Bugzilla 2.16
Comment 7•24 years ago
|
||
I saw this once before when i searched for the number, but I see no evidence
that that is the case from the error. If your theory is correct that this is a
number that has been rounded down, it could easily occur in multiple places.
Comment 8•23 years ago
|
||
This should probably be closed out at some point in time unless we can
reproduce it.
Assignee: tara → justdave
Component: Bugzilla → Bugzilla-General
OS: Windows NT → All
Product: Webtools → Bugzilla
Hardware: PC → All
Version: other → 2.10
Updated•23 years ago
|
Whiteboard: midair
Comment 9•23 years ago
|
||
Closing WFM.
Gerv
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 10•23 years ago
|
||
clearing milestone for invalid/wontfix/worksforme/duplicate so they'll show up
as untriaged if they get reopened.
Target Milestone: Bugzilla 2.16 → ---
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•