-
Notifications
You must be signed in to change notification settings - Fork 181
Populate Transitions in Transition Events (continuation) #1269
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
base: rolling
Are you sure you want to change the base?
Populate Transitions in Transition Events (continuation) #1269
Conversation
Signed-off-by: CursedRock17 <[email protected]>
Signed-off-by: CursedRock17 <[email protected]>
Signed-off-by: CursedRock17 <[email protected]>
Signed-off-by: SuperJappie08 <[email protected]>
Signed-off-by: SuperJappie08 <[email protected]>
Signed-off-by: SuperJappie08 <[email protected]>
Signed-off-by: SuperJappie08 <[email protected]>
Signed-off-by: SuperJappie08 <[email protected]>
|
Pulls: ros2/rcl_interfaces#185, #1269, ros2/rclcpp#2967, ros2/rclpy#1528 |
|
@fujitatomoya, this patch did not yet include compatibility with ros2/rcl_interfaces#185, but I have it (just not part of the PR yet) I will fix it now |
Adds compatibility with ros2/rcl_interfaces#185 Signed-off-by: SuperJappie08 <[email protected]>
Description
Original author: @CursedRock17
Original reviewers: @fujitatomoya @audrow @ivanpauno @wjwwood
Continuation of #1140.
Implemented most feedback.
Fixes #1019
Is this user-facing behavior change?
Yes, Lifecycle transition events are now filled.
This comes with a small change in function signatures to support timestamping.
Did you use Generative AI?
No.
Additional Information
I would also recommend merging ros2/rcl_interfaces#185 to limit the amount of breaking changes.
I noticed that the
node_handlefield ofrcl_lifecycle_com_interface_tis never filled or used as far as I can see.