Uh oh!
There was an error while loading. Please reload this page.
err: document ABORT_ERR code - #36319
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
nodejs-github-bot
commented
Dec 1, 2020
nodejs-github-bot
commented
Dec 1, 2020
There was a problem hiding this comment.
| ### `ABRT_ERR` | |
| ### `ABRT_ERR` | |
| <!-- YAML | |
| added: v15.0.0 | |
| --> |
?
There was a problem hiding this comment.
Technically it's not 15.0 and this code existed on DOMException beforehand and users could craft it. The actual non DOMException AbortError is 15.2 - I am not sure what this should say?
There was a problem hiding this comment.
I think it should say whatever is the first version in which Node.js actually throws errors with this code.
There was a problem hiding this comment.
What version first had DOMException? 8?
There was a problem hiding this comment.
I'm a bit confused about this code. Could you point me to where it is defined? I cannot find any occurence of ABRT_ERR in the source code.
There was a problem hiding this comment.
@targos wow, we all missed the typo - it's ABORT_ERR and not ABRT_ERR.
I'll push a fix, the error is defined in two places - in internal/errors.j (as class AbortError extends Error {) and in lib/internal/per_context/domexception.js.
There was a problem hiding this comment.
Oh, I didn't even think it could be a typo!
So I checked and v15.0.0 is indeed the first version where we throw errors with that code. I don't think we should mention versions where users could somehow do it themselves.
nodejs-github-bot
commented
Dec 2, 2020
nodejs-github-bot
commented
Dec 2, 2020
nodejs-github-bot
commented
Dec 3, 2020
nodejs-github-bot
commented
Dec 4, 2020
nodejs-github-bot
commented
Dec 4, 2020
nodejs-github-bot
commented
Dec 5, 2020
We added an `AbortError` with the same code and name as the web's as part of the consensus in nodejs#36084 but never actually documented the error in our error codes list. This PR adds the error code.
6152951 to
dde4ae4Comparebenjamingr
commented
Dec 7, 2020
I think this probably needed a rebase 🤔 |
nodejs-github-bot
commented
Dec 7, 2020
nodejs-github-bot
commented
Dec 7, 2020
nodejs-github-bot
commented
Dec 8, 2020
nodejs-github-bot
commented
Dec 8, 2020
benjamingr
commented
Dec 9, 2020
Landed in a2a2ff3 |
Trott
commented
Dec 9, 2020
This commit was added to master without metadata. Not sure there's much to do at this point other than notify @nodejs/releasers so they can work around it in releases. (Actually, I'd be OK with a force push to fix if there was consensus on @nodejs/tsc. It's been 6 hours so far....) |
gireeshpunathil
commented
Dec 9, 2020
+1 to force-push. |
Trott
commented
Dec 9, 2020
When I rebase against master, I scan the new commits to see what's been landed. I never use the bring-master-up-to-date feature in node-core-utils and always do it manually before landing anything specifically so I can do this quick scan. |
Trott
commented
Dec 9, 2020
In addition to no metadata, it also has an invalid subsystem ( |
We added an `AbortError` with the same code and name as the web's as part of the consensus in #36084 but never actually documented the error in our error codes list. This PR adds the error code. PR-URL: #36319 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
Trott
commented
Dec 9, 2020
Force pushed to fix metadata and subsystem stuff. Landed in 13e2170 |
benjamingr
commented
Dec 9, 2020
@Trott thanks, what did I do wrong? (Next commands are: I rant lint & tests and then pushed) |
targos
commented
Dec 9, 2020
You have to answer "Yes" to this question, otherwise the commit message is not amended, so the metadata is not added to it About the subsystem, I thought it was validated by |
benjamingr
commented
Dec 9, 2020
Thanks, my bad. I thought that it's not possible to land stuff with I'll just check the commit log before pushing the next few times in case there is more stuff I miss. |
We added an `AbortError` with the same code and name as the web's as part of the consensus in #36084 but never actually documented the error in our error codes list. This PR adds the error code. PR-URL: #36319 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
We added an `AbortError` with the same code and name as the web's as part of the consensus in #36084 but never actually documented the error in our error codes list. This PR adds the error code. PR-URL: #36319 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
We added an `AbortError` with the same code and name as the web's as part of the consensus in #36084 but never actually documented the error in our error codes list. This PR adds the error code. PR-URL: #36319 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
We added an
AbortErrorwith the same code and name as the web's aspart of the consensus in #36084 but
never actually documented the error in our error codes list.
This PR adds the error code.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes