Add JavaException as a crash annotation
Categories
(Toolkit :: Crash Reporting, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox85 | --- | fixed |
People
(Reporter: royang, Assigned: royang, NeedInfo)
Details
Attachments
(2 files, 2 obsolete files)
Bug 1671654 - Add JavaException annotation for determining the cause of a Java exception. r=gsvelto!
47 bytes,
text/x-phabricator-request
|
Details | Review | |
1.82 KB,
text/plain
|
Details |
Adding JavaException annotation for reporting stacktrace in a structured format.
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
Assignee | ||
Comment 3•4 years ago
|
||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Comment on attachment 9182064 [details]
Data Review.txt
Data Review Form (to be filled by Data Stewards)
-
Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
Yes, in CrashAnnotations.yaml. -
Is there a control mechanism that allows the user to turn the data collection on and off?
Yes, -
If the request is for permanent data collection, is there someone who will monitor the data over time?
Roger and the a-c team. -
Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Type 1 -
Is the data collection request for default-on or default-off?
Determined by the client -
Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?
No -
Is the data collection covered by the existing Firefox privacy notice?
Yes -
Does there need to be a check-in in the future to determine whether to renew the data?
No -
Does the data collection use a third-party collection tool?
No
Assignee | ||
Comment 5•4 years ago
|
||
Comment 6•4 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:royang, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 7•4 years ago
•
|
||
Sorry, I had to change the data review category about couple weeks ago. I'll ping the data reviewer again. Thanks
Hey Emily,
This request is Cat 3 so I wanted to escalate it and have you take a look. Thank you!
Comment 9•3 years ago
|
||
Hi - sorry for the delay. What cat 3 data might be collected?
Thanks!
Assignee | ||
Comment 10•3 years ago
•
|
||
Hi Emily, The Cat 3 data is that the Exception Message might include URL information with possible PII information. Thanks,
Comment 11•3 years ago
|
||
OK, thanks for explaining further. If this is new collection, to the extent this is applicable, can you please ensure it's disclosed here: https://firefox-source-docs.mozilla.org/toolkit/crashreporter/crashreporter/index.html
Otherwise, fine wit me!
Emily
Assignee | ||
Comment 12•3 years ago
|
||
Thanks!
Comment 13•3 years ago
|
||
Pushed by smolnar@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9cf25eadcf55 Add JavaException annotation for determining the cause of a Java exception. r=gsvelto
Comment 14•3 years ago
|
||
bugherder |
Assignee | ||
Comment 15•1 year ago
|
||
Comment 16•1 year ago
|
||
Comment on attachment 9317760 [details]
Bug 1671654 - Add bypass load URI delegate in load flags. r=jonalmeida
Revision D169865 was moved to bug 1809269. Setting attachment 9317760 [details] to obsolete.
Description
•