On-wire incompatibility when using rmw_zenoh_cpp between RoboStack ROS Jazzy default install and apt ROS Jazzy default install since 2025-06-29 #93
Description
On 2025-06-29 the rmw_zenoh_cpp on the main apt/deb official channel of ROS Jazzy was updated to 0.2.5, that is not anymore on wire compatible with earlier versions (i.e. <= 0.2.3), see https://discourse.ros.org/t/wire-breaking-change-in-rmw-zenoh-for-ros-2-jazzy/44367 .
In a nutshell, this means that if a users install ROS Jazzy with .deb packages on a machine, and ROS Jazzy with RoboStack on another machine, if it tries to communicate, the node will crash with errors like:
[robot_state_publisher-5] thread 'rx-7' panicked at library/core/src/panicking.rs:136:5:
[robot_state_publisher-5] panic in a function that cannot unwind
[robot_state_publisher-5] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[robot_state_publisher-5] thread caused non-unwinding panic. aborting.
[rviz2-3] thread 'rx-5' panicked at library/core/src/panicking.rs:136:5:
[rviz2-3] panic in a function that cannot unwind
[rviz2-3] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[rviz2-3] thread caused non-unwinding panic. aborting.
[gzserver-1] thread 'rx-1' panicked at library/core/src/panicking.rs:136:5:
[gzserver-1] panic in a function that cannot unwind
[gzserver-1] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[gzserver-1] thread caused non-unwinding panic. aborting.
The best solution is to update also RoboStack's rmw_zenoh_cpp with a good old full rebuild/sync.