Skip to content

[NVBUG 7115760] Rebuild Lyrical against Zenoh 1.10.2 - #236

Closed
aayoung-nv wants to merge 1 commit into
RoboStack:mainfrom
aayoung-nv:fix/lyrical-zenoh-1.10.2
Closed

aayoung-nv wants to merge 1 commit into
RoboStack:mainfrom
aayoung-nv:fix/lyrical-zenoh-1.10.2

Conversation

@aayoung-nv

Copy link
Copy Markdown

Summary

Draft: native package build and runtime validation remain outstanding.

Build Lyrical against conda-forge libzenohc and libzenohcxx 1.10.2 instead of 1.10.1. Keep the change in distros/lyrical/; other distributions retain their current pins.

Zenoh 1.10.2 includes the StartConditions deadlock correction in eclipse-zenoh/zenoh#2779, which closes eclipse-zenoh/zenoh#2581. The conda-forge 1.10.1 package source lacks that correction. Related upstream ROS work: ros2/rmw_zenoh#1069.

Lyrical's vendor uses USE_SYSTEM_ZENOH=ON. This updates the system library pins; it deliberately leaves the ROS release snapshot unchanged. Whether these rebuilt packages resolve the observed Windows composed-Nav2 discovery/RPC stall still needs a native A/B test without queue overrides.

Rebuild scope

The repository's vinca-rebuild-plan reports 735 affected packages out of 1,253 selected packages. Direct users are zenoh_cpp_vendor and rmw_zenoh_cpp. Because this exceeds the 50% threshold, use the repository's conservative full-rebuild policy:

  • Global build number 30 -> 35, above the checked released/per-package maxima.
  • Mutex 0.22.0 -> 0.23.0.
  • Remove 21 per-package build-number overrides; retain unrelated CMake settings.
  • Set Lyrical's temporary PR control full_rebuild: true.

This scope follows the dependency planner, not a measured ABI break in every dependent. An ABI-backed smaller rebuild would need separate validation. Reset the temporary PR cache controls after merging, per repository guidance.

conda_build_config.yaml was regenerated with pixi run rs lyrical render-pinning, not edited by hand.

Local validation

  • pixi run rs check.
  • pixi run test: 83 passed.
  • git diff --check.
  • Focused render-only dependency solves for libzenohc ==1.10.2 plus libzenohcxx ==1.10.2 on win-64 and linux-64 with Lyrical's generated variant configuration.
  • Compare full Lyrical dependency reports under old and proposed pins: JSON reports are identical. Both fail with the existing libopencv, pcl, py-opencv, and qt-main conflicts, plus the same libcamera note. This is not a full dependency-check pass.
  • Build the vendor and RMW against 1.10.2 and inspect their package constraints/ABI compatibility.
  • Repeat discovery/RPC stress and the Windows Nav2 route with rebuilt packages and no queue override.
  • Complete the supported-platform rebuild and CI.

No full native rebuild was started locally. Dependency solves are not binary or runtime validation.

Signed-off-by: aayoung <aayoung@nvidia.com>
@aayoung-nv aayoung-nv closed this Nov 19, 2026
@aayoung-nv
aayoung-nv deleted the fix/lyrical-zenoh-1.10.2 branch November 19, 2026 18:53
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.

Persistent routing lock stall/deadlock under peer churn

1 participant