BugWatch properties should be reset when the watch's remotebug field is updated.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug 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:/
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.
description: | updated |
description: | updated |
This is a bit bizarre. According to the bug watch, the last status pulled for the bug was "RESOLVED DUPLICATE," which it's never had, according to the history presented by Bugzilla. It should update again in 24 hours or so. When it does, we'll see what status is getting imported for it. At the moment, I can't reproduce this locally.
I'll mark this Incomplete as a reminder to check the watch again tomorrow.