You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hash 930dea5c8de47d47ac0b3814ee1c08bac8a70c22 (Fix component arguments to be inline with service. (#220)) + rclcpp_components from binaries version 0.7.0.
DDS implementation:
RTI Connext
Client library (if applicable):
N/A
Steps to reproduce issue
From a terminal, run rclcpp_components:
ros2 run rclcpp_components component_container
From a second terminal, add some components (tested with 2 talkers and 2 listeners):
Does the problem disappear when passing --spin-time N with a long enough period to ensure the node started by ros2 component list has enough time to complete discovery?
I need to rebuild by workspace with the current packages to retest properly; right now it is heppening to me even with --spin-time 10, but I want to make sure it's not a local issue. I'll try again and post the results here.
@dirk-thomas I can't reproduce this issue anymore using an up-to-date workspace from source.
For completion I tried listing the components 20 times in a row with FastRTPS, OpenSplice and Connext and it didn't fail even a single time. --spin-time N option wasn't required.
Bug report
Required Info:
930dea5c8de47d47ac0b3814ee1c08bac8a70c22
(Fix component arguments to be inline with service. (#220)
) +rclcpp_components
from binaries version0.7.0
.Steps to reproduce issue
rclcpp_components
:The interaction between talkers and listeners should be displayed in the first terminal, e.g:
Expected behavior
Components should be listed like this:
Actual behavior
~20% of the times, no component is listed.
Additional information
This doesn't seem to happen in
fastrtps
noropensplice
.The text was updated successfully, but these errors were encountered: