Error reports should have list of oops messages separate from req_vars
Bug #488950 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
The only way for a script to provide information in oopses about the context in which the oops occurred is to abuse the req_vars for this purpose. This is done either via a ScriptRequest, or through the new oopsMessage mechanism.
Instead, oops reports should contain a list of oops messages, and oops tools should interpret them accordingly.
| Changed in launchpad-foundations: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in launchpad-foundations: | |
| assignee: | nobody → Edwin Grubbs (edwin-grubbs) |
| Changed in launchpad-foundations: | |
| status: | Triaged → In Progress |
| Changed in launchpad: | |
| assignee: | Edwin Grubbs (edwin-grubbs) → nobody |
| Changed in launchpad: | |
| status: | In Progress → Triaged |
To post a comment you must log in.
