#1551 closed defect (fixed)
Base handler error handling gets confused when the request is bad
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Core (Other) | Version: | 0.91 |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I don't know exactly what circumstances cause this, but the exception handling in base.py can lose track of the important exception to display in the error email. If an exception is thrown from repr(request) at about line 114, then it is that exception which is displayed rather than the original one that invoked the exception handling in the first place.
The solution is to get a copy of the first exception before beginning the handling, so it can be explicitly passed to _get_traceback.
Attachments (1)
Change History (2)
by , 18 years ago
comment:1 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The patch!