Log a more verbose error message in the console when a abuse report fails for a client or server submission error
Categories
(Toolkit :: Add-ons Manager, task, P2)
Tracking
()
People
(Reporter: rpl, Assigned: rpl)
References
Details
Attachments
(3 files)
|
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
|
23.44 KB,
image/png
|
Details | |
|
7.96 KB,
image/png
|
Details |
To make it easier to investigate issues related to "report submit" errors the AbuseReport's submit method should log a more verbose error message in the browser console.
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 1•6 years ago
|
||
Depends on D32625
Comment 3•6 years ago
|
||
| bugherder | ||
Comment 4•6 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 5•6 years ago
|
||
Marking as qe-verify-, this change is tested as part of the automated tests.
Comment 6•6 years ago
|
||
Is this something which should be considered for Beta uplift or can it ride the trains?
Comment 7•6 years ago
|
||
Verified as fixed in latest FF Nightly, Windows 10x64 and macOS 10.14.5
Please see post fix screenshot attached.
Updated•6 years ago
|
Comment 8•6 years ago
|
||
| Assignee | ||
Comment 9•6 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #6)
Is this something which should be considered for Beta uplift or can it ride the trains?
It wouldn't be strictly necessary, but it has been helpful to investigate the reasons behind reports that the API endpoint rejects, and so it would be nice to have it.
I initially marked this as qe-verify- as it is tested in automation and it doesn't fix any particular issue for a user, but QA used the verbose error recently and so I asked them to verify this bug explicitly.
| Assignee | ||
Comment 10•6 years ago
|
||
Comment on attachment 9067986 [details]
Bug 1552787 - Log a more verbose error message in the console when a abuse report fails for a client or server submission error. r?mixedpuppy!
Beta/Release Uplift Approval Request
- User impact if declined: No visible impact (but it makes easier to provide useful details if a user is not able to report an abuse for a particular extension and wants to report the issue to us on bugzilla).
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: Not strictly necessary to verify manually, as it is tested in automation, but QA can also verify it on beta, e.g. by changing the abuse report url from about:config ("extensions.abuseReport.url") to point it to a fake API endpoint that always returns an HTTP error on any report submission.
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): The change shouldn't be risky as it is restricted to the abuse report error reporting and tested in automation.
- String changes made/needed:
| Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 11•6 years ago
|
||
Comment on attachment 9067986 [details]
Bug 1552787 - Log a more verbose error message in the console when a abuse report fails for a client or server submission error. r?mixedpuppy!
debugging help for addon abuse report errors, approved for 68.0b10
Updated•6 years ago
|
Comment 12•6 years ago
|
||
| bugherder uplift | ||
Comment 13•6 years ago
|
||
Verified as fixed in 68.0b12 .
I will attach a postfix screenshot
Updated•6 years ago
|
Comment 14•6 years ago
|
||
Description
•