set thread names by node in component container isolated#2871
Merged
ahcorde merged 9 commits intoros2:rollingfrom Jun 18, 2025
Merged
set thread names by node in component container isolated#2871ahcorde merged 9 commits intoros2:rollingfrom
ahcorde merged 9 commits intoros2:rollingfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Set the thread name of each node's thread in
component_container_isolated. This should support POSIX platforms, Apple, and Windows. I tested on Linux only so far.Fixes #2818
Is this user-facing behavior change?
User's may see an additional warning if the thread name couldn't set for whatever reason. If users are looking at custom thread names, then they will see a difference.
Did you use Generative AI?
Yes with Cursor autocomplete.
Additional Information