Closed
Bug 1042365
Opened 11 years ago
Closed 11 years ago
UndefinedError: list object has no element Undefined
Categories
(Socorro :: Webapp, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: peterbe, Assigned: peterbe)
References
()
Details
Getting this on the report index. Error seems to do with template rendering.
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → peterbe
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•11 years ago
|
||
Likely guilty commit https://github.com/mozilla/socorro/commit/7c4d4be61e8b7fd6a1c1a8c3c34f28547671d647
(cc :ted)
| Assignee | ||
Comment 2•11 years ago
|
||
The reason for this is that if a report contains a `json_dump` instead of the (older) `dump` and that `json_dump` doesn't have a `crash_info.crashing_thread` it failed in jinja.
PR https://github.com/mozilla/socorro/pull/2237
Comment 3•11 years ago
|
||
Commits pushed to master at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/f9a15091d4b86f12933e9e9d2e09e30aa190f64e
bug 1042365 - some parsed_dumps don't have crash_info.crashing_thread
https://github.com/mozilla/socorro/commit/6fecdd54cee2ebf4761f3c0e441e571451572bfa
Merge pull request #2237 from peterbe/bug-1042365-some-parsed_dumps-dont-have-crash_infocrashing_thread
bug 1042365 - some parsed_dumps don't have crash_info.crashing_thread
| Assignee | ||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 4•11 years ago
|
||
It's still happening :(
For example https://crash-stats.mozilla.com/report/index/6d1ea37b-3c53-42e7-84ec-566f72130906
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 5•11 years ago
|
||
The way we handle these old dumps has changed a lot since this was reopened.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•