-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lib: clean up usage of threw #10534
lib: clean up usage of threw #10534
Conversation
lib/timers.js
Outdated
} finally { | ||
if (!threw) return; | ||
|
||
} catch (ex) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The exception is no longer thrown now, is this wanted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, looks like @JacksonTian forgot to rethrow the ex
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much. fixed it.
hmm... @Fishrock123 are you familiar with why |
I think this is a performance optimization of some sort. This should be profiled. (e.g. |
I hold the change of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Requesting the aforementioned profiling)
@Fishrock123 How to profiling it? Hope to get some suggestions. |
ping @Fishrock123 ... any updates on this one? |
@JacksonTian this needs a rebase. And can you please comment when you did? There is no notification otherwise and I see that you rebased the last time you were asked to. |
7c4d19f
to
802c7b8
Compare
rebased. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM if CI is green
I benchmarked this recently and could not find any difference performance wise. |
No reaction and the performance should not be affected
Landed in d56a82dfc3569332b1ad5a3249b8ca3405c37163 |
The test actually fails and I just force pushed to remove the commit again. |
It doesn't look like there were any CI runs for this so good call backing it out. Bonus points for it being within the 10 minute window ;-) |
I knew why I said
I somewhat had a bad feeling about it but I forgot to run it right before I pushed. |
Oh. Let's run CI again? |
Use try/catch to instead of threw.
Sorry, My mistake. After rebased with master, the test message no more need update. Now I removed it. |
Landed in 67d792a |
Use try/catch to instead of threw. PR-URL: #10534 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Use try/catch to instead of threw. PR-URL: nodejs#10534 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Use try/catch to instead of threw. PR-URL: nodejs/node#10534 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Use try/catch to instead of threw. PR-URL: #10534 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Use try/catch to instead of threw. PR-URL: #10534 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Use try/catch to instead of threw. PR-URL: #10534 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
backported to v6.x Let me know if it should be backed out |
Use try/catch to instead of threw. PR-URL: #10534 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
bootstrap_node, module, timers