Skip to content

fix: multi-part services names being mangled incorrectly#66

Open
Carter12s wants to merge 1 commit intoZettaScaleLabs:mainfrom
Carter12s:fix-service-long-names
Open

fix: multi-part services names being mangled incorrectly#66
Carter12s wants to merge 1 commit intoZettaScaleLabs:mainfrom
Carter12s:fix-service-long-names

Conversation

@Carter12s
Copy link
Contributor

I believe this is an appropriate fix for #65 , but I'm not certain.

@CLAassistant
Copy link

CLAassistant commented Jan 15, 2026

CLA assistant check
All committers have signed the CLA.

@Carter12s Carter12s changed the title Fix multi-part services names being mangled incorrectly Fix: multi-part services names being mangled incorrectly Jan 15, 2026
@Carter12s Carter12s changed the title Fix: multi-part services names being mangled incorrectly fix: multi-part services names being mangled incorrectly Jan 15, 2026
@0x53A
Copy link
Contributor

0x53A commented Jan 27, 2026

I can confirm that this works - with the change, I can subscribe to a ROS2 Jazzy instance with rmw_zenoh_cpp. The same issue happens with topic names, not just service names.

On the ROS side, we are publishing sensor_msgs/Imu to /imu/data.
Without the change, we wouldn't receive any data on the rust side. With the change, it works.

I dumped all zenoh keys:

@/db1b671e2ed38b958740c13a0832dd93/router/publisher/0/imu/data/sensor_msgs::msg::dds_::Imu_/RIHS01_7d9a00ff131080897a5ec7e26e315954b8eae3353c3f995c55faf71574000b5b

@/ded286d03cb4abba3d16bc12daaa28f5/peer/publisher/0/imu/data/sensor_msgs::msg::dds_::Imu_/RIHS01_7d9a00ff131080897a5ec7e26e315954b8eae3353c3f995c55faf71574000b5b

As you can see, the publishers are not encoding the slashes.

0x53A added a commit to 0x53A/ros-z that referenced this pull request Jan 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants