Activity log for bug #294719

Date Who What changed Old value New value Message
2008-11-06 15:03:56 Ursula Junque bug added bug
2008-11-06 15:12:33 Curtis Hovey launchpad-registry: status New Triaged
2008-11-06 15:12:33 Curtis Hovey launchpad-registry: assignee bradcrittenden
2008-11-06 15:12:33 Curtis Hovey launchpad-registry: statusexplanation Hi brad, since this has come up at the same time that we were discussing the privacy, do you have time to close this bug for this cycle?
2008-11-06 15:12:33 Curtis Hovey launchpad-registry: milestone 2.1.11
2008-11-07 14:33:09 Curtis Hovey launchpad-registry: importance Undecided High
2008-11-07 14:33:09 Curtis Hovey launchpad-registry: statusexplanation Hi brad, since this has come up at the same time that we were discussing the privacy, do you have time to close this bug for this cycle?
2008-11-07 14:54:31 Curtis Hovey launchpad-registry: assignee bradcrittenden edwin-grubbs
2008-11-07 14:54:31 Curtis Hovey launchpad-registry: statusexplanation This looks like a race condition. We may need to understand what the user was doing to reproduce the problem.
2008-11-20 18:38:14 Edwin Grubbs launchpad-registry: statusexplanation This looks like a race condition. We may need to understand what the user was doing to reproduce the problem.
2008-11-20 18:38:14 Edwin Grubbs launchpad-registry: milestone 2.1.11 2.1.12
2008-11-20 22:28:14 Edwin Grubbs launchpad-registry: importance High Medium
2008-11-20 22:28:14 Edwin Grubbs launchpad-registry: statusexplanation I am unable to recreate this issue, and it hasn't happened again since Nov 7, so I am going to change the importance to Medium. If it is just an absurdly unlikely timing issued that caused these oopses, one fix is to use database triggers to enforce these constraints. However, that may be overkill for something that should be extremely rare.
2008-11-20 23:22:00 Edwin Grubbs launchpad-registry: status Triaged Incomplete
2008-11-20 23:22:00 Edwin Grubbs launchpad-registry: statusexplanation I am unable to recreate this issue, and it hasn't happened again since Nov 7, so I am going to change the importance to Medium. If it is just an absurdly unlikely timing issued that caused these oopses, one fix is to use database triggers to enforce these constraints. However, that may be overkill for something that should be extremely rare. I double-checked with Joey about his steps for reproducing it, and I was unable to get it to work, so I am marking it incomplete.
2008-11-20 23:22:00 Edwin Grubbs launchpad-registry: milestone 2.1.12
2009-01-01 16:49:33 Curtis Hovey launchpad-registry: importance Medium Low
2009-01-01 16:49:33 Curtis Hovey launchpad-registry: assignee edwin-grubbs
2009-01-01 16:49:33 Curtis Hovey launchpad-registry: statusexplanation I double-checked with Joey about his steps for reproducing it, and I was unable to get it to work, so I am marking it incomplete. I suspect this report will be marked invalid when Launchpad addresses the core issue that private teams must not leak their names.
2009-05-06 22:47:18 Curtis Hovey launchpad-registry: status Incomplete Invalid