Deprecate the experimental EventsExecutor#3192
Conversation
|
Tick the box to add this pull request to the merge queue (same as
|
|
Pulls: #3192 |
ahcorde
left a comment
There was a problem hiding this comment.
I can see one warning https://ci.ros2.org/job/ci_linux-aarch64/22485/clang-tidy/
fixed in 3cb984c |
fujitatomoya
left a comment
There was a problem hiding this comment.
lgtm with green CI
|
Pulls: #3192 |
Signed-off-by: Skyler Medeiros <skye@polymathrobotics.com>
Signed-off-by: Skyler Medeiros <skye@polymathrobotics.com>
Signed-off-by: Skyler Medeiros <skye@polymathrobotics.com>
Signed-off-by: Skyler Medeiros <skye@polymathrobotics.com>
Signed-off-by: Janosch Machowinski <J.Machowinski@cellumation.com>
Signed-off-by: Skyler Medeiros <skye@polymathrobotics.com>
7ff14d3 to
0bee264
Compare
|
@jmachowinski - I think the hanging I can get the test to pass by changing the hanging |
|
https://github.com/Mergifyio backport lyrical |
✅ Backports have been createdDetails
Cherry-pick of 5272750 has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
Description
This PR adds a compile-time deprecation warning when using the experimental EventsExecutor, warning to switch to the new Callback Group Events Executor in single-threaded mode instead.
Tests which exercise the EventsExecutor have deprecation warnings disabled while it is still in the source tree.
Also replaces one usage of the old executor with the new one in
rclcpp_action/test_server.cpp.Fixes # (issue)
Is this user-facing behavior change?
Users will now get a compiler warning when using the experimental EventsExecutor in their application code
Did you use Generative AI?
Claude Opus 4.8 was used to identify spots in the codebase where the deprecation warning suppression should be introduced.
Additional Information
This ought to be backported to at least Lyrical