-
Notifications
You must be signed in to change notification settings - Fork 181
[Iron]Add ~/get_type_description service (rep2011) (backport #1052)
#1082
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
Conversation
* Add ~/get_type_description service API * Add node type cache * Register subscription, publication, service and action types with node type cache * Add functions to convert between rosidl_runtime_c / type_description_interfaces structs RCL does not initialize the get_type_description service itself, instead providing a full enough API for full language clients to initialize it and register its callback within their threading/execution framework Signed-off-by: Hans-Joachim Krauch <[email protected]> Signed-off-by: Emerson Knapp <[email protected]> (cherry picked from commit a4633b8)
Signed-off-by: Emerson Knapp <[email protected]>
|
Pulls: #1082 |
clalancette
left a comment
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.
I've left just one comment to think about. This otherwise looks good to me.
Signed-off-by: Emerson Knapp <[email protected]>
|
Pulls: #1082, ros2/rclcpp#2236, ros2/system_tests#521, ros2/rclpy#1140, ros2/ros2cli#839 |
~/get_type_description service (rep2011) (backport #1052)~/get_type_description service (rep2011) (backport #1052)
This is an automatic backport of pull request #1052 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com