| 2010-08-16 08:04:17 |
era |
bug |
|
|
added bug |
| 2010-08-16 08:04:49 |
era |
description |
Don't know how or whether this is a general problem, but bug #188422 recently (2010-08-15 03:04:48) changed to "Invalid" even though the only recent change to the upstream bug was to change it from UNCONFIRMED to NEW -- along with some other minor changes; full transcript at https://bugzilla.gnome.org/show_activity.cgi?id=553929 |
Don't know how or whether this is a general problem, but the linked upstream Gnome bug in bug #188422 recently (2010-08-15 03:04:48) changed to "Invalid" even though the only recent change to the upstream bug was to change it from UNCONFIRMED to NEW -- along with some other minor changes; full transcript at https://bugzilla.gnome.org/show_activity.cgi?id=553929
|
|
| 2010-08-16 08:05:06 |
era |
description |
Don't know how or whether this is a general problem, but the linked upstream Gnome bug in bug #188422 recently (2010-08-15 03:04:48) changed to "Invalid" even though the only recent change to the upstream bug was to change it from UNCONFIRMED to NEW -- along with some other minor changes; full transcript at https://bugzilla.gnome.org/show_activity.cgi?id=553929
|
Don't know how or whether this is a general problem, but the task linked to the upstream Gnome bug in bug #188422 recently (2010-08-15 03:04:48) changed to "Invalid" even though the only recent change to the upstream bug was to change it from UNCONFIRMED to NEW -- along with some other minor changes; full transcript at https://bugzilla.gnome.org/show_activity.cgi?id=553929
|
|
| 2010-08-16 08:22:08 |
Graham Binns |
malone: status |
New |
Incomplete |
|
| 2010-08-17 10:27:06 |
era |
marked as duplicate |
|
222870 |
|
| 2010-08-17 10:27:42 |
era |
removed duplicate marker |
222870 |
|
|
| 2010-08-19 13:07:17 |
Graham Binns |
malone: importance |
Undecided |
High |
|
| 2010-08-19 13:07:20 |
Graham Binns |
malone: status |
Incomplete |
Triaged |
|
| 2010-08-19 20:21:49 |
Graham Binns |
summary |
Upstream Gnome bug mysteriously changed to "Invalid" |
BugWatch properties should be reset when the watch's remotebug field is updated. |
|
| 2010-08-19 20:23:25 |
Graham Binns |
description |
Don't know how or whether this is a general problem, but the task linked to the upstream Gnome bug in bug #188422 recently (2010-08-15 03:04:48) changed to "Invalid" even though the only recent change to the upstream bug was to change it from UNCONFIRMED to NEW -- along with some other minor changes; full transcript at https://bugzilla.gnome.org/show_activity.cgi?id=553929
|
Don't know how or whether this is a general problem, but the task linked to the upstream Gnome bug in bug #188422 recently (2010-08-15 03:04:48) changed to "Invalid" even though the only recent change to the upstream bug was to change it from UNCONFIRMED to NEW -- along with some other minor changes; full transcript at https://bugzilla.gnome.org/show_activity.cgi?id=553929
As Bryce discovered, this is because the bug watch's remotebug value was updated but because of the way we deal with remote watches (not updating if they haven't changed remotely), the watch was never updated.
Solution:
The solution is to do the following when BugWatch.remotebug is altered:
* lastchanged -> None
* lastchecked -> None
* remotestatus -> None
* remoteimportance ->
* last_error_type -> None
* next_check -> datetime.now(). (We could maybe set it to None and let the scheduler take care of it, though)
We should also clear the BugWatchActivity entries for the BugWatch, since they're no longer relevant. |
|
| 2012-01-05 04:56:29 |
Robert Collins |
tags |
lp-bugs |
lp-bugs trivial |
|
