Search This Blog

17 September 2009

Eraser ...

I let a couple of these pass by but just thought I'd mention it (just in case any other ex-MySQLer is experiencing anything similar...

Why does the MySQL bugs system remove former employees from the historical record?

Date: Thu, 17 Sep 2009 20:26:35 +0200
From: Bug Database
Subject: #29838 [Csd]: myisam corruption using concurrent select ... and update
In-reply-to:
X-Originating-IP: [140.98.193.23]
To: antony.curtis@ieee.org
Message-id: <200909171826.n8HIQZU6002514@bugs.mysql.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8BIT
X-Bug: 29838
X-Bug-URL: http://bugs.mysql.com/29838
X-Bug-Category: Server: MyISAM
References:
X-Authentication-warning: bugs.mysql.com: apache set sender to
bounce+antony.curtis=ieee.org@bugs.mysql.com using -f

Dear developer, the bug assigned to you for review has been re-assigned to .

Updated by: James Day
Reported by: Shane Bester
Category: Server: MyISAM
Severity: S2 (Serious)
Status: Closed
Changeset: http://lists.mysql.com/commits/31944
Version: 4.0.30, 4.1.23, 5.0.46BK, 5.1BK, 6.0.1
OS: Any
Tags: concurrent_insert, error 127, corruption
Assigned To: Ingo Strüwing
Priority: P1 (Critical)
-Affected issues: 17915,16700,15911,15439,17046,15681,15442,14965,16745,18487,15427,18623,19293,21309,23978,23763
+Affected issues: 17915,16700, 15911,15439, 17046,15681, 15442,14965,
16745,18487, 15427,18623, 19293,21309, 23978,23763
-Reviewer: Antony Curtis [done]
+Reviewer: Bugs System [done]

Reviewer: Sergey Vojtovich [done]
Internal Tags: sr5_1
Affects customer: Yes
Triage:

[No new comments]

4 comments:

datacharmer said...

Nothing is removed from historical records. The bugs system maintains track of everything.
What you see is a late administrative action. You were assigned as reviewer for that particular bug. Since you are not an employee anymore, you were removed from that role.
Now, we have a rule that only employees can be reviewers and I believe we should change that, but this is a different story and at the moment the reason for that change is a simple administrative cleanup.

Giuseppe

Antony said...

Hmm ok.

Still strange that these old closed bugs are being edited.

Oh well.

jim said...

the real edit was to add something to the list of affected support issues.

the reviewer change is just a side-effect of you no longer being among the list of reviewers -- that means that the editing form defaulted to an empty reviewer and it got changed when the form was submitted.

the change in reviewers wasn't deliberate.

Antony said...

Thanks Jim... That makes sense.