http 500 error doesn't contain a stack trace
Bug #1364481 reported by
Blake Rouse
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Raphaël Badin | ||
Bug Description
We used to show all stack traces for errors. This was recently changed so it was not returned to the client, which is nice except for 500 errors.
I now cannot find out what went wrong with my code. All I get is: 'NoneType' object has no attribute 'items'
This makes it really hard to track down where this is occurring.
Related branches
lp:~rvb/maas/traceback-error-500
- Blake Rouse (community): Approve
-
Diff: 121 lines (+24/-24)3 files modifiedsrc/maas/settings.py (+0/-2)
src/maasserver/middleware.py (+12/-10)
src/maasserver/tests/test_middleware.py (+12/-12)
| Changed in maas: | |
| milestone: | none → 1.7.0 |
| Changed in maas: | |
| assignee: | nobody → Raphaël Badin (rvb) |
| status: | Confirmed → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
