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
Fix: Add namespace isolation to prevent cross-namespace route creation
When a bridge is configured with a non-root namespace (e.g., "/bot1"),
it was incorrectly creating local DDS entities for remote announcements
from different namespaces (e.g., "bot2/chatter"). This caused topics to
appear in `ros2 topic list` but fail when subscribed, due to Zenoh key
expression mismatch during data routing.
This fix adds namespace validation in all Announced event handlers:
- AnnouncedMsgPub/Sub
- AnnouncedServiceSrv/Cli
- AnnouncedActionSrv/Cli
New behavior:
- Bridges with namespace="/bot1" only handle routes for "bot1/*" keys
- Bridges with namespace="/" (default) accept all routes (backward compatible)
- Remote announcements from other namespaces are ignored with debug logging
This enforces proper namespace isolation, ensuring bridges only create
routes for their own namespace scope.
0 commit comments