| 2009-02-06 07:19:57 |
Paul Hummer |
bug |
|
|
added bug |
| 2009-02-06 07:20:09 |
Paul Hummer |
launchpad-bazaar: status |
New |
Triaged |
|
| 2009-02-06 07:20:09 |
Paul Hummer |
launchpad-bazaar: importance |
Undecided |
Low |
|
| 2009-02-06 07:20:09 |
Paul Hummer |
launchpad-bazaar: statusexplanation |
|
|
|
| 2009-02-20 01:43:04 |
Jonathan Lange |
launchpad-bazaar: importance |
Low |
High |
|
| 2009-02-20 01:43:04 |
Jonathan Lange |
launchpad-bazaar: statusexplanation |
|
It's telling users they've screwed up when they haven't and generating OOPSes. This is enough to make it a high priority bug.
Surely we can come up with something that will stop the errors without requiring substantial changes to our data model! |
|
| 2009-02-20 01:44:03 |
Jonathan Lange |
description |
This is a weird edge case, but one that I think is worth filing a bug for.
So I did a code review for Entertainer and sent it, then immediately merged the branch into trunk and pushed up to launchpad. The scanner apparently marked the BMP as merged before my review with ' status approved' could get handled. This resulted in this oops: https://devpad.canonical.com/~matsubara/oops.cgi/2009-02-06/CEMAIL5
If nothing else, maybe we should just catch the exception and silently pass an changing the status if it's in a state that doesn't make sense to go "back" to approved for (like non-final states). |
This is a weird edge case, but one that I think is worth filing a bug for.
So I did a code review for Entertainer and sent it, then immediately merged the branch into trunk and pushed up to launchpad. The scanner apparently marked the BMP as merged before my review with ' status approved' could get handled. This resulted in this oops: https://devpad.canonical.com/~matsubara/oops.cgi/2009-02-06/CEMAIL5
If nothing else, maybe we should just catch the exception and silently pass an changing the status if it's in a state that doesn't make sense to go "back" to approved for (like non-final states).
See OOPS-1138CEMAIL12 |
|
| 2009-02-20 01:45:23 |
Diogo Matsubara |
description |
This is a weird edge case, but one that I think is worth filing a bug for.
So I did a code review for Entertainer and sent it, then immediately merged the branch into trunk and pushed up to launchpad. The scanner apparently marked the BMP as merged before my review with ' status approved' could get handled. This resulted in this oops: https://devpad.canonical.com/~matsubara/oops.cgi/2009-02-06/CEMAIL5
If nothing else, maybe we should just catch the exception and silently pass an changing the status if it's in a state that doesn't make sense to go "back" to approved for (like non-final states).
See OOPS-1138CEMAIL12 |
This is a weird edge case, but one that I think is worth filing a bug for.
So I did a code review for Entertainer and sent it, then immediately merged the branch into trunk and pushed up to launchpad. The scanner apparently marked the BMP as merged before my review with ' status approved' could get handled. This resulted in this oops: OOPS-1133CEMAIL5
If nothing else, maybe we should just catch the exception and silently pass an changing the status if it's in a state that doesn't make sense to go "back" to approved for (like non-final states).
Recently: OOPS-1138CEMAIL12 |
|
| 2009-02-20 01:45:23 |
Diogo Matsubara |
title |
OOPS on InvalidStateTransition when reviewing code by mail |
OOPS on BadStateTransition when reviewing code by mail |
|
| 2009-04-07 21:48:41 |
Ursula Junque |
description |
This is a weird edge case, but one that I think is worth filing a bug for.
So I did a code review for Entertainer and sent it, then immediately merged the branch into trunk and pushed up to launchpad. The scanner apparently marked the BMP as merged before my review with ' status approved' could get handled. This resulted in this oops: OOPS-1133CEMAIL5
If nothing else, maybe we should just catch the exception and silently pass an changing the status if it's in a state that doesn't make sense to go "back" to approved for (like non-final states).
Recently: OOPS-1138CEMAIL12 |
This is a weird edge case, but one that I think is worth filing a bug for.
So I did a code review for Entertainer and sent it, then immediately merged the branch into trunk and pushed up to launchpad. The scanner apparently marked the BMP as merged before my review with ' status approved' could get handled. This resulted in this oops: OOPS-1133CEMAIL5
If nothing else, maybe we should just catch the exception and silently pass an changing the status if it's in a state that doesn't make sense to go "back" to approved for (like non-final states).
Recently: OOPS-1138CEMAIL12, OOPS-1192CEMAIL4 |
|
| 2009-06-12 19:37:34 |
Aaron Bentley |
launchpad-code: status |
Triaged |
Fix Committed |
|
| 2009-06-12 19:37:34 |
Aaron Bentley |
launchpad-code: assignee |
|
Aaron Bentley (abentley) |
|
| 2009-07-02 20:08:18 |
Aaron Bentley |
launchpad-code: status |
Fix Committed |
Fix Released |
|
