-
Notifications
You must be signed in to change notification settings - Fork 341
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
Test failures: subscription already associated with a wait set #1101
Comments
👀 @bmagyar they confirmed in the linked PR that this is not possible any more. You said you have a different approach for the test structure? |
@dhood as you brought yourself into the topic, do you maybe have an idea how to fix that temporarily? |
yes, curiosity got the better of me, I'm a sucker for CI that needs troubleshooting 😇 Perhaps explicitly removing the subscription from the waitset after it's been waited on, in wait_for? might be hanging onto a reference by the time the spin_some gets called. I opened #1106 hoping it would run CI for me but no such luck. Otherwise an alternate approach to avoid waitsets could be an async wait on the underlying rt_command_ptr_ to be set away from null (in combination with spin_until_future_complete), but not as nice. Maybe something else is possible with the default callback group of the node not having that parameter true that William mentioned, but I imagine it would affect something else on those nodes accidentally..? |
fixed with #1206 (kudos to @saikishor) |
in rolling builds
https://github.com/ros-controls/ros2_controllers/actions/runs/8728644425/job/23948909083?pr=1100
and in debian source build
https://github.com/ros-controls/ros2_controllers/actions/runs/8728644426/job/23948908730
might be related to ros2/rclcpp#2142
The text was updated successfully, but these errors were encountered: