-
Notifications
You must be signed in to change notification settings - Fork 76
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
Append ros namespace to target container if available. #429
base: rolling
Are you sure you want to change the base?
Conversation
Signed-off-by: Mukunda Bharatheesha <[email protected]>
ae1920c
to
f5671d3
Compare
# Check if a global ros_namespace has been set with push ros namespace. | ||
base_ns = context.launch_configurations.get('ros_namespace', None) | ||
if base_ns is not None: | ||
self.__final_target_container_name = make_namespace_absolute( |
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 will be applied to the service client to load the composable nodes below.
without having this fix, service path is not appended with namespace, that fails to call the load request for target container.
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.
Pulls: #429 |
This PR introduces a change to fix #428.
With this change, when a composable node is loaded into a target container that is running under a
ros_namespace
set using<push_ros_namespace>
, the target container name gets prefixed withros_namespace
using theLaunchContext
. This enables the composable nodes to load into a namespaced target container.How did I test this:
apt install ros-rolling-image-tools
ros2 node list
Without the changes in this PR, the output from the launch would be:
And the composable nodes wouldn't show up with
ros2 node list