ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
There's a solution in this PR:
https://github.com/ros-planning/moveit2/pull/1272
A quick-and-dirty fix is to move long-running callbacks into a detached thread, like in this rclcpp demo: https://github.com/AndyZe/examples/blob/14c743af8bbca6a40e83da7a470c5332dce66d9d/rclcpp/actions/minimal_action_server/member_functions.cpp#L110
The PR is based on that idea.
2 | No.2 Revision |
There's a solution in this PR:
https://github.com/ros-planning/moveit2/pull/1272
A quick-and-dirty fix is to move long-running callbacks into a detached thread, like in this rclcpp demo: https://github.com/AndyZe/examples/blob/14c743af8bbca6a40e83da7a470c5332dce66d9d/rclcpp/actions/minimal_action_server/member_functions.cpp#L110
The PR is based on that idea.And also to make sure each action server (if you have several) has its own callback group.