-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
src: set a default thread name for workers #4664
src: set a default thread name for workers #4664
Conversation
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.
This looks good to me with Saúl suggestion and tests and documentation added
40806db
to
6670a2c
Compare
I'm currently working on tests to make it more reliable than it is nowadays (there's a chance of a thread not being called executed from the thread pool). |
82e78cc
to
2d16a9d
Compare
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. Left some nits.
6e10efe
to
e0d951a
Compare
Hello,
I'm opening this to discuss if that's feasible from libuv point of view. I'm working on nodejs/node#56416 and hardcoding libuv thread names seems something reasonable (I have also talked with @santigimeno previously).
So, I'm opening it here and if I get a green light I can work on tests