Closed
Bug 871597
Opened 12 years ago
Closed 12 years ago
[socorro-crashstats] getCrash calls that yield a 404 should be more helpful on the front-end
Categories
(Socorro :: Webapp, task)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: peterbe, Assigned: peterbe)
Details
Attachments
(1 file)
|
44.44 KB,
image/png
|
Details |
Crash Not Found page
If we try to reach a raw crash ID for something that doesn't exist in the HBase, we should not just return a 404. It would be much more helpful with a human readable error message says the crash could not be found.
For example, on https://crash-stats-django.allizom.org/report/index/fd2266f0-9d0c-4ce1-b5a6-523092130313 the link to this page existed because the postgres had the Crash ID but the dev HBase lacks the crash.
|
Assignee | |
Comment 1•12 years ago
|
||
Hmm... this appears to be a matter of regression. We already have code to cover this scenario.
Assignee: nobody → peterbe
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•12 years ago
|
||
Sigh. My bad. It's not a bug or regression. If you try to reach a Crash ID that does NOT exist in HBase you already get a nice error (see attached screenshot). I just looked too quickly and thought it was the "Page Not Found" error.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
|
|
Assignee | |
Comment 3•12 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•