global search oopses from incomplete XML
Bug #246932 reported by
Curtis Hovey
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Curtis Hovey | ||
Bug Description
I see several oopses over the past few days like OOPS-920A433. They appear to be caused when the Google response XML is incomplete, or may be empty. Retries of the URL work, so I suspect connectivity may be factor.
We may want to catch these problems and show a message explaining that data was not available, and that the search should be tried again.
Related OOPSes: OOPS-1020F2123, OOPS-1059A3034
| Changed in launchpad: | |
| status: | New → Confirmed |
| description: | updated |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in launchpad-foundations: | |
| assignee: | nobody → sinzui-is |
| importance: | Undecided → High |
| milestone: | none → 2.1.11 |
| status: | Confirmed → Triaged |
| Changed in launchpad-foundations: | |
| milestone: | 2.1.11 → 2.1.12 |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #2 |
| Changed in launchpad-foundations: | |
| status: | Triaged → In Progress |
| description: | updated |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #3 |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #4 |
| Changed in launchpad-foundations: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #5 |
| Changed in launchpad-foundations: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We should update the error in the oopses to be clear when incomplete XML was returned to Launchpad. The user should see an explanation in the pagematches location that the search was not returned, but it can be tried again.