exception asking to report a bug should specify a summary
Bug #380973 reported by
Martin Pool
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
| Breezy |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
When bzr hits an unexpected exception it asks users to report a bug. Many of them do so, but many of these bugs have poor summaries which slows down processing and detection of duplicates. bzr should suggest filing a report with a summary like "TypeError in get_foo()" or "TypeError in get_foo running bzr status".
apport may have some code to do this or it could be pulled out of the traceback.
Also, it could help to put the bottom of the stacktrace into the crash message.
| description: | updated |
| tags: | added: crash-reporting easy |
| Changed in bzr: | |
| assignee: | Martin Pool (mbp) → nobody |
Revision history for this message
| Martin Pool (mbp) wrote | #1 |
| tags: | added: check-for-breezy |
| tags: | removed: check-for-breezy |
| Changed in brz: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
To post a comment you must log in.
I guess the easiest way to get this is to look at the string form of the traceback.