-
Notifications
You must be signed in to change notification settings - Fork 160
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
Ensure ros2doctor ROS nodes have valid names. #513
Conversation
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
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! I think as long as we can enforce node name uniqueness this should be fine
For a test, we could try using |
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
@claireyywang @jacobperron PTAL. I changed tests' layout a bit as the existing ones where not testing anything. I'd think there was some confusion w.r.t On a side note, I find the |
Oof, I didn't realize that. I wonder if there are other places in our code base that make a similar mistake. |
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 with green CI
Focal PR job failure is unrelated. Have two approvals. Merging. |
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com> Signed-off-by: Craig <CraigUkaea@gmail.com>
Precisely what the title says. Came across this while testing
ros2 doctor hello
on a VM that had dashes in its hostname. It's tricky one to test for regression, so I'm open to ideas.