-
Notifications
You must be signed in to change notification settings - Fork 168
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
Add warning and annotation to ros2 node list
when there are non-unique nodes
#462
Add warning and annotation to ros2 node list
when there are non-unique nodes
#462
Conversation
f11d96f
to
cd57c9c
Compare
@ros2/aws-oncall - please run this CI job |
@mjcarroll perhaps, review? |
cd57c9c
to
75d398b
Compare
@chapulina who should we ask for OSRF-side review on this PR? |
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
@hidmic can you review this? |
418ea4c
to
d26c103
Compare
@wjwwood uploaded a simplified version of this PR |
Signed-off-by: Emerson Knapp <emerson.b.knapp@gmail.com>
d26c103
to
b66cf91
Compare
I approved the changes, can one of you all do CI again (since there were new changes) and then I (or anyone really) can merge it. |
Hypothesis confirmed, @wjwwood i think we're good to go? |
First half of #453
First half of https://github.com/ros-tooling/aws-roadmap/issues/196
Add a simple warning, and annotate which nodes it applies to, when
ros2 node list
lists multiple nodes with the same exact name. Within the "request for design" discussion ros2/design#187, there was confusion expressed about where multiple names come from, whether they are artifacts of the printing process. This at least clears that up a little bit -it does not change the functionality at all.