-
Notifications
You must be signed in to change notification settings - Fork 227
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
Wait Set Index Too Big #1381
Comments
Could you try using FastDDS (instead of cyclone_dds) to check if the problem still occurs in your environment ? |
Sure. I can give this a shot. Would service call would cause a QoS event added to the wait set? This seems to be the source of the bug. |
Neither cyclone_dds or fastrtps_cpp works. |
While creating publisher and subscription, you can set event_callbacks. BTW, how did you determine it's related to the QoS Event? rclpy/rclpy/src/rclpy/wait_set.cpp Lines 157 to 197 in b488272
|
Bug report
Required Info:
Steps to reproduce issue
Expected behavior
Actual behavior
Additional information
I cannot provide the code I am using to allow you to reproduce this bug, but it is a rclpy process that has a single MultiThreadedExecutor. The executor spins three nodes, and always gets hung up on this self.executor.spin_until_future_complete(self.future) with a wait set index bug.
Any advice on how to approach this problem would be much appreciated.
Feature request
Feature description
Implementation considerations
The text was updated successfully, but these errors were encountered: