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
Hi! The bug was quite similar to this. We just switched from zenoh-plugin-dds to zenoh-plugin-ros2dds to bridge ROS 2 messages. This time ROS distribution Humble is used and CycloneDDS as RMW_IMPLEMENTATION. However, the issue persists as the one occurred in this. One bridge is randomly unable to discover ROS node which are set up within the same virtual network.
What's more, even if switching back to zenoh-plugin-dds, using humble and CycloneDDS, the issue still persists. I think the issue had never been resolved:(
Describe the bug
Hi! The bug was quite similar to this. We just switched from
zenoh-plugin-dds
tozenoh-plugin-ros2dds
to bridge ROS 2 messages. This time ROS distributionHumble
is used andCycloneDDS
asRMW_IMPLEMENTATION
. However, the issue persists as the one occurred in this. One bridge is randomly unable to discover ROS node which are set up within the same virtual network.What's more, even if switching back to
zenoh-plugin-dds
, usinghumble
andCycloneDDS
, the issue still persists. I think the issue had never been resolved:(To reproduce
Docker Compose file:
System info
Platform: Ubuntu 20.04 64-bit
Zenoh: 0.10.0-rc
ROS2: humble
Docker: Docker Engine - Community(version 24.0.5 )
The text was updated successfully, but these errors were encountered: