Closed
Bug 1716543
Opened 3 years ago
Closed 3 years ago
Annotate nsStandardURL::SanityCheck crash reports
Categories
(Core :: Networking: HTTP, task, P2)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
91 Branch
People
(Reporter: valentin, Assigned: valentin)
Details
(Whiteboard: [necko-triaged])
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
2.53 KB,
text/plain
|
chutten
:
data-review+
|
Details |
No description provided.
Assignee | ||
Comment 1•3 years ago
|
||
Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/0da59114555d Annotate nsStandardURL::SanityCheck with URL offsets r=necko-reviewers,kershaw
Comment 3•3 years ago
|
||
Shouldn't this get data review?
Assignee | ||
Comment 4•3 years ago
|
||
Thanks for the heads-up. This is my first time adding an annotation.
Attachment #9227668 -
Flags: data-review?(jcristau)
Updated•3 years ago
|
Attachment #9227668 -
Flags: data-review?(jcristau) → data-review?(chutten)
Comment 5•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox91:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
Comment 6•3 years ago
|
||
Comment on attachment 9227668 [details]
crashannotation_URLSegments_datarequest.md
DATA COLLECTION REVIEW RESPONSE:
Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?
Yes.
Is there a control mechanism that allows the user to turn the data collection on and off?
Yes. This collection is Telemetry so can be controlled through Firefox's Preferences.
If the request is for permanent data collection, is there someone who will monitor the data over time?
Yes, Valentin Gosu is responsible.
Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 1, Technical.
Is the data collection request for default-on or default-off?
Default on for all channels.
Does the instrumentation include the addition of any new identifiers?
No.
Is the data collection covered by the existing Firefox privacy notice?
Yes.
Does the data collection use a third-party collection tool?
No.
Result: datareview+
Attachment #9227668 -
Flags: data-review?(chutten) → data-review+
Assignee | ||
Comment 7•3 years ago
|
||
Comment on attachment 9227164 [details]
Bug 1716543 - Annotate nsStandardURL::SanityCheck with URL offsets r=#necko
Beta/Release Uplift Approval Request
- User impact if declined: Lack of visibility into reason for nsStandardURL sanity check assertions (bug 1715960)
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This code path already crashes (intentionally). This patch merely adds relevant offsets to the crash annotations.
- String changes made/needed:
Attachment #9227164 -
Flags: approval-mozilla-beta?
Comment 8•3 years ago
|
||
Comment on attachment 9227164 [details]
Bug 1716543 - Annotate nsStandardURL::SanityCheck with URL offsets r=#necko
approved for 90.0b11
Attachment #9227164 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Comment 9•3 years ago
|
||
bugherder uplift |
status-firefox90:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•