fix: Expose timers used by rclcpp::Waitables#2699
Conversation
|
Added a fix for the expire timer not working for action servers. |
335fbe4 to
c172276
Compare
|
This pull request has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/next-client-library-wg-meeting-friday-6th-december-2024-8am-pt/40954/2 |
alsora
left a comment
There was a problem hiding this comment.
The changes look good.
Would you mind adding a couple of unit-tests that exercise the new method?
It would be ideal to have:
- a test for the action server to verify that it returns 1 timer
- a test with the events executor where we verify that the timer is correctly handled
f6651f9 to
35694c8
Compare
35694c8 to
f0ee613
Compare
mjcarroll
left a comment
There was a problem hiding this comment.
Changes LGTM with green CI.
|
Pulls: #2699 |
|
@ahcorde this commit depends on ros2/rcl#1201, so we need a custom gist. |
|
Pulls: #2699, ros2/rcl#1201 |
f0ee613 to
8e984ec
Compare
|
Pulls: #2699, ros2/system_tests#556, ros2/rcl#1201 |
8e984ec to
f924997
Compare
|
Pulls: #2699, ros2/system_tests#556, ros2/rcl#1201 |
This change was needed, as an events based executors needs to be aware of the timers, in order generate the timer ready events. Signed-off-by: Janosch Machowinski <J.Machowinski@cellumation.com>
This should fix a bug, were the internal expire timer of the action server was not triggered. Signed-off-by: Janosch Machowinski <J.Machowinski@cellumation.com>
Signed-off-by: Janosch Machowinski <J.Machowinski@cellumation.com>
f924997 to
2747640
Compare
|
Pulls: #2699, ros2/system_tests#556, ros2/rcl#1201 |
|
CI checks out. |
|
Hey! @jmachowinski @ahcorde, this PR introduced an issue in Rolling CI: #2731 |
This change was needed, as an events based executors needs to be aware of the timers, in order generate the timer ready events.
@alsora @wjwwood This PR is the followup to the discussion two weeks back in the client workgroup.