Bug watch updater will try to update invalid bug watches forever
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Graham Binns |
Bug Description
The bug watch updater keeps no state between runs, so if someone enters an invalid bug id then that invalid bug watch will be probed every day for ever.
This also means that errors that we might need to deal with a buried in a torrent of "Didn't find bug" error messages.
First step in solving this is to reduce this error message down to an INFO - we expect this situation to happen so it isn't an error, and our code should eventually cope with it.
At the moment we determine whether or not to check a BugWatch based on the time elapsed since its lastchecked date. Once bug 538095 has landed we should alter BugTracker.
NB: There are many smaller fixes that need to be made for this bug to be considered fixed and those fixes will be tracked individually. We can fix this bug when all other bugs tagged story-bug-
[1] https:/
Changed in malone: | |
status: | Unconfirmed → Confirmed |
tags: | added: story-reliable-bug-syncing |
description: | updated |
tags: | added: story-bug-watch-error-tracking |
description: | updated |
Changed in malone: | |
status: | In Progress → Fix Committed |
assignee: | nobody → Graham Binns (gmb) |
tags: | added: qa-ok |
Changed in malone: | |
status: | Fix Committed → Fix Released |
I don't agree with bumping down the errors into INFO until the code can cope with invalid watches. The reason is that I use the updater output to go in and garden the bug watches that are wrong. I agree that we need better reporting of these, but I don't think we're there yet, and I'm not sure if it will be a short-term priority.
I have been changing to zero the ID of bug watches that are /really/ invalid. If you could delete those, Stuart, I'd appreciate it. I can then vouch to keep the error log output at zero there!