Return service from node_type_description_service_init#1112
Merged
Return service from node_type_description_service_init#1112
Conversation
This makes the caller responsible for cleaning up the service. Signed-off-by: Michael Carroll <mjcarroll@intrinsic.ai>
54a4d99 to
43dfecc
Compare
Signed-off-by: Michael Carroll <mjcarroll@intrinsic.ai>
mjcarroll
commented
Oct 27, 2023
Signed-off-by: Michael Carroll <mjcarroll@intrinsic.ai>
added 2 commits
October 28, 2023 02:33
Signed-off-by: Michael Carroll <mjcarroll@intrinsic.ai>
Signed-off-by: Michael Carroll <mjcarroll@intrinsic.ai>
Member
Author
|
This was referenced Oct 28, 2023
Member
Author
|
One more run after some rebase/force-push:
|
This was referenced Oct 30, 2023
clalancette
added a commit
that referenced
this pull request
Jun 25, 2024
In particular, make sure to match all service_description_init with the appropriate finis. While we are in here, also add in a "service_not_exists" function that will quit much earlier, speeding up the test. This is essentially a backport of #1107 and parts of #1112, but adapted for Iron. Signed-off-by: Chris Lalancette <clalancette@gmail.com>
clalancette
added a commit
that referenced
this pull request
Jun 25, 2024
In particular, make sure to match all service_description_init with the appropriate finis. While we are in here, also add in a "service_not_exists" function that will quit much earlier, speeding up the test. This is essentially a backport of #1107 and parts of #1112, but adapted for Iron. Signed-off-by: Chris Lalancette <clalancette@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This changes the mechanism of
rcl_node_type_description_service_initto populate a user-provided service.This makes it the calling user's responsibility to call
rcl_service_finion the returned service, making it more in line with the rest of therclAPI.This was discovered when working with the new
rclcpp::WaitSetimplementation.The main issue is that the executor needs to share ownership with objects that it is
wait-ing on for the entire duration of thewait, even if a node is removed from the executor at that time. That is, the executor doesn't have knowledge of the nodes so much as the waitable objects in the collection.In this current implementation, the type_description was being
fini-ed during theNodeTypeDescriptionsdestructor here: https://github.com/ros2/rclcpp/blob/fcbe64cff4bea3109531254ceb2955dc4b1bb320/rclcpp/src/rclcpp/node_interfaces/node_type_descriptions.cpp#L128-L139. This could cause a situation where a service is cleaned up while we are still waiting on it, and yields a segfault afterwards.After discussion with @clalancette, it seems the better approach is to have the user init the service and then be responsible for managing the lifetime of that service through their client library (eg
rclcpp::Service)