Uh oh!
There was an error while loading. Please reload this page.
url: improve invalid url performance - #49692
Conversation
nodejs-github-bot
commented
Sep 17, 2023
Review requested:
|
0501c68 to
79415edCompareanonrig
commented
Sep 17, 2023
@nodejs/tsc I've removed the Safari returns: None of them have the |
aduh95
commented
Sep 17, 2023
I would keep the input, and even add the base, it can very hard to understand what is the error without seeing the input and base |
Uh oh!
There was an error while loading. Please reload this page.
rluvaton
commented
Sep 18, 2023
aduh95
commented
Sep 18, 2023
Could there be a way to get the same performance improvements without removing helpful debugging information? If not, maybe we could use a flag to opt-in to the slower option that outputs the |
anonrig
commented
Sep 18, 2023
Probably, although I'm not sure. This requires a similar approach to what |
nodejs-github-bot
commented
Sep 18, 2023
nodejs-github-bot
commented
Sep 18, 2023
tniessen
commented
Sep 19, 2023
FWIW, I tend to agree with @aduh95 that removing error information for the sake of performance (on an error path!) does not benefit users. I thought that |
Uzlopak
commented
Sep 19, 2023
How much is actually the performance hit when keeping the input as an attribute? |
BridgeAR
left a comment
There was a problem hiding this comment.
I do not think it's a good idea to remove important debug information in favor of performance. We can definitely improve the performance but debug information is more important. I had an open PR to improve the situation a lot and I have to get back to that again.
147dd75 to
a9c408aCompareanonrig
commented
Sep 19, 2023
a9c408a to
29267d9Compare29267d9 to
c59b136Comparenodejs-github-bot
commented
Sep 20, 2023
nodejs-github-bot
commented
Sep 20, 2023
nodejs-github-bot
commented
Sep 20, 2023
nodejs-github-bot
commented
Sep 21, 2023
anonrig
commented
Sep 22, 2023
Hey @BridgeAR, can you re-review this pull request, and remove your block? |
benjamingr
commented
Sep 23, 2023
I suspect he would still object since the URL isn't part of the message string, what's the cost of adding that back? |
I don't follow. URL was never part of the message string? Input is a property of the error object. On top of that I've also added base property to the error as well. |
benjamingr
commented
Sep 23, 2023
@anonrig ah, I'm probably mixing it up with another PR then, lgtm |
anonrig
commented
Sep 26, 2023
Adding to @nodejs/tsc agenda to resolve the block. |
targos
commented
Sep 26, 2023
There's no need for the TSC to intervene if you addressed the blocking comment |
nodejs-github-bot
commented
Sep 26, 2023
Landed in c829c03 |
PR-URL: #49692 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Robert Nagy <ronagy@icloud.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
PR-URL: #49692 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Robert Nagy <ronagy@icloud.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
PR-URL: nodejs#49692 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Robert Nagy <ronagy@icloud.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Some easy wins for
Invalid URLpath.cc @nodejs/url @nodejs/performance