-
Notifications
You must be signed in to change notification settings - Fork 227
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
Addition of a wait_for_node()
function
#823
Comments
+1 for a function like this, but if I understand correctly, ros2/rcl#907 looks for publisher/subscriber counts on a named topic, right? Which is close enough in spirit, but I guess that isn't the API this issue would want to have wrapped in |
Right. The implementation I have in ros2/launch_ros#263 is pretty basic, and definitely not efficient. Not sure where to implement this feature though, maybe in |
I think that's the way to go because I see utility for all of the |
FYI I think this has been closed by #930! That has been released into Iron (not backported into Humble AFAICT) |
Good call. I'll go ahead and close this one out, thanks! |
Feature request
Feature description
It would be nice to have a
wait_for_node(node_name, timeout)
function which would wait for a particular node to show up, and block for a specified time. Further, we can have a set ofwait_for_*
functions which could wait for parameters, services, topics to show up.Implementation considerations
This feature was mentioned in ros2/launch_ros#263.
Related feature exists in
rcl
(ros2/rcl#907) but it hasn't been ported torclcpp
(ros2/rclcpp#1621) due to a design issue.The text was updated successfully, but these errors were encountered: