IOUtils unknown errors do not report the nsresult error code
Categories
(Toolkit Graveyard :: OS.File, defect, P3)
Tracking
(firefox96 fixed)
| Tracking | Status | |
|---|---|---|
| firefox96 | --- | fixed |
People
(Reporter: beth, Assigned: beth)
Details
Attachments
(1 file)
|
48 bytes,
text/x-phabricator-request
|
Details |
When IOUtils encounters an error that it has not yet mapped in IOUtils::RejectJSPromise, it will only include the error code in the message if the IOError was constructed without a message.
Ideally, we would like to include this error code so that we can then add more mapping of nsresult errors we encounter to DOMExceptions.
| Assignee | ||
Comment 1•4 years ago
|
||
Presently, if IOUtils encounters an error that it does not know how to map to
a DOMException (via RejectJSPromise), it will only include the nsresult error
code if the IOError was constructed without a message. This hides the root
cause of errors.
Now we always include the error code when rejecting with an UnknownError.
Comment 3•4 years ago
|
||
Backed out 3 changesets (Bug 1741247, Bug 1723082, Bug 1736175) for causing PathUtils.normalize failures.
Backout link: https://hg.mozilla.org/integration/autoland/rev/72c397486d4cec809c954f4be3df881c2db93d56
Push with failures, failure log.
Comment 5•4 years ago
|
||
| bugherder | ||
| Assignee | ||
Updated•4 years ago
|
Updated•2 years ago
|
Description
•