You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rclpy humble and foxy (but bug may exist in others)
Steps to reproduce issue
ros2 run examples_rclpy_minimal_action_server server
ros2 topic echo /fibonacci/_action/status
ros2 action send_goal /fibonacci example_interfaces/action/Fibonacci '{}'
Expected behavior
topic_echo should show status 1 (ACCEPTED) and then status 2 (EXECUTING)
Actual behavior
It jumps straight to EXECUTING
Additional information
This isn't just a problem with topic echo or the example node, I also have the same problem with my HMI (which uses the ActionClient) and my custom ros2 node.
Just FYI, ros2 run examples_rclpy_minimal_action_server server is not appropriate example to defer the goal execution, instead we could use ros2 run examples_rclpy_minimal_action_server server_defer which implements handle_accepted_callback.
even with server_defer, we can observe the reported behavior with rolling branch.
Bug report
Steps to reproduce issue
Expected behavior
topic_echo
should show status 1 (ACCEPTED) and then status 2 (EXECUTING)Actual behavior
It jumps straight to EXECUTING
Additional information
This isn't just a problem with topic echo or the example node, I also have the same problem with my HMI (which uses the ActionClient) and my custom ros2 node.
A workaround is (for humble):
Or (for foxy)
And then give this callback to the ActionServer
The text was updated successfully, but these errors were encountered: