Closed
Bug 807349
Opened 12 years ago
Closed 12 years ago
add new 'exploitability' column to 'reports'
Categories
(Socorro :: Database, task)
Tracking
(Not tracked)
RESOLVED
FIXED
26
People
(Reporter: lars, Assigned: selenamarie)
References
Details
(Whiteboard: [qa-])
a new text column 'exploitablity' should added to the 'reports' table. It may have to be added to the 'reports_clean' table, too (still checking on that). We can likely defer that to the future.
The possible values are NULL, 'none', 'interesting', 'low', 'medium', 'high'. I'm loath to make this an enum because I don't trust that this is really as static list over time. Therefore a TEXT column datatype may be most appropriate. I'll defer to your judgment but reserve the right to say I told you so.
Reporter | ||
Updated•12 years ago
|
Target Milestone: --- → 28
Comment 1•12 years ago
|
||
FWIW the strings derive from an actual enum on the C++ side of Breakpad:
http://code.google.com/p/google-breakpad/source/browse/trunk/src/google_breakpad/processor/process_state.h#52
I wouldn't expect that to change since it's pretty hard to get finer-grained info there.
Assignee | ||
Comment 2•12 years ago
|
||
https://github.com/mozilla/socorro/pull/926
If this is needed on reports_clean, we'll make it an enum there.
Assignee | ||
Updated•12 years ago
|
Whiteboard: [qa-]
Comment 3•12 years ago
|
||
Commits pushed to master at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/ed3a2127ddc5a8daf9eab49eca532b74ef74fac8
Bug 807349 - exploitability column add
https://github.com/mozilla/socorro/commit/fd8bd42f6c227b817e65036c263ce3a3cd9bd202
Merge pull request #926 from selenamarie/bug807349-exploitability-db-changes
Bug 807349 - exploitability column add
Assignee | ||
Updated•12 years ago
|
Target Milestone: 28 → 27
Assignee | ||
Updated•12 years ago
|
Target Milestone: 27 → 28
Updated•12 years ago
|
Target Milestone: 28 → 26
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•12 years ago
|
||
This needs to be applied when the processors and monitor are offline. Takes seconds, but only if nothing is accessing the reports table.
![]() |
||
Comment 5•12 years ago
|
||
(In reply to Selena Deckelmann :selenamarie :selena from comment #4)
> This needs to be applied when the processors and monitor are offline. Takes
> seconds, but only if nothing is accessing the reports table.
Has this been deployed? When I'm logged in, I can't seem to find the exploitability column under Reports, but I can see the exploitability rating of each individual report.
Comment 6•12 years ago
|
||
This is just about adding a column to a database table. It has nothing to do with adding it to reports in the UI.
![]() |
||
Comment 7•12 years ago
|
||
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #6)
> This is just about adding a column to a database table. It has nothing to do
> with adding it to reports in the UI.
Filed bug 826564 to add it to reports in the Socorro web UI.
You need to log in
before you can comment on or make changes to this bug.
Description
•