SourceForge ExternalBugTracker doesn't handle non-existent bugs
Bug #227380 reported by
Graham Binns
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Steve Kowalik |
Bug Description
Although fixing bug 183737 allowed checkwatches to handle private SourceForge bugs properly, we don't yet handle non-existent bugs on SourceForge properly (see OOPS-982CCW3576). This is partly due to the fact that non-existent bugs cause a completely different form of error message to be returned and partly due to the fact that SourceForge returns a 200 OK for non-existent bugs (we already handle the case of a 404).
The SourceForge ExternalBugTracker should be updated to deal with these errors.
description: | updated |
Changed in malone: | |
status: | Incomplete → Triaged |
To post a comment you must log in.
Hi Graham, are you sure OOPS-857CCW1 is the right one? It seems to be an oops related to Mantis.