Skip to content

Bump Zenoh to v1.3.2 and improve e2e reliability with HeartbeatSporadic #591

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Apr 4, 2025

Conversation

JEnoch
Copy link
Contributor

@JEnoch JEnoch commented Apr 4, 2025

This PR updates Zenoh to v1.3.2, making the following changes of commit ids:

It includes those notable changes:

In addition, the PR also makes the RELIABLE + TRANSIENT_LOCAL Publishers and Subscribers to use the new non periodic last sample miss detection mechanism for Advanced pub/sub. This ensures end-to-end reliability for those topics, and fixes #543.

@Yadunund Yadunund changed the title Bump Zenoh to v1.3.2 Bump Zenoh to v1.3.2 and improve e2e reliability with HeartbeatSporadic Apr 4, 2025
Copy link
Member

@Yadunund Yadunund left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good. Will run CI before merging.

@Yadunund
Copy link
Member

Yadunund commented Apr 4, 2025

Ci started with: https://gist.githubusercontent.com/Yadunund/c4074b12ea5bdedcddae7b60f60c34bc/raw/0a2dfaf7d380d0733c673af4e6f9773e7261fdfd/ros2_ci.repos

  • Linux Build Status
  • Linux-aarch64 Build Status -> Flaky ros2 param test
    • Linux-aarch64 Build Status
  • Linux-rhel Build Status
  • Windows Build Status

@Yadunund Yadunund merged commit a9ab960 into ros2:rolling Apr 4, 2025
5 checks passed
@Yadunund
Copy link
Member

Yadunund commented Apr 4, 2025

@Mergifyio backport jazzy humble

Copy link

mergify bot commented Apr 4, 2025

backport jazzy humble

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Apr 4, 2025
…ic (#591)

* Bump zenoh-c to ffa4bdd, zenoh-cpp to 868fdad and zenoh to 3f62ebc

* Apply same config changes than eclipse-zenoh/zenoh#1825

* Apply same config changes than eclipse-zenoh/zenoh#1850

* For RELIABLE+TRANSIENT_LOCAL topics, enable sample_miss_detection and recovery for end-to-end reliability

(cherry picked from commit a9ab960)
mergify bot pushed a commit that referenced this pull request Apr 4, 2025
…ic (#591)

* Bump zenoh-c to ffa4bdd, zenoh-cpp to 868fdad and zenoh to 3f62ebc

* Apply same config changes than eclipse-zenoh/zenoh#1825

* Apply same config changes than eclipse-zenoh/zenoh#1850

* For RELIABLE+TRANSIENT_LOCAL topics, enable sample_miss_detection and recovery for end-to-end reliability

(cherry picked from commit a9ab960)
Yadunund pushed a commit that referenced this pull request Apr 5, 2025
…ic (#591) (#593)

* Bump zenoh-c to ffa4bdd, zenoh-cpp to 868fdad and zenoh to 3f62ebc

* Apply same config changes than eclipse-zenoh/zenoh#1825

* Apply same config changes than eclipse-zenoh/zenoh#1850

* For RELIABLE+TRANSIENT_LOCAL topics, enable sample_miss_detection and recovery for end-to-end reliability

(cherry picked from commit a9ab960)

Co-authored-by: Julien Enoch <[email protected]>
Yadunund pushed a commit that referenced this pull request Apr 5, 2025
…ic (#591) (#594)

* Bump zenoh-c to ffa4bdd, zenoh-cpp to 868fdad and zenoh to 3f62ebc

* Apply same config changes than eclipse-zenoh/zenoh#1825

* Apply same config changes than eclipse-zenoh/zenoh#1850

* For RELIABLE+TRANSIENT_LOCAL topics, enable sample_miss_detection and recovery for end-to-end reliability

(cherry picked from commit a9ab960)

Co-authored-by: Julien Enoch <[email protected]>
@Timple
Copy link
Contributor

Timple commented Apr 5, 2025

Nice to see this is merged!

There is only a few days left before the Kilted freeze: https://discourse.ros.org/t/upcoming-rmw-feature-freeze-for-ros-2-kilted-kaiju-on-april-7-2025/43020

Could we get a new release which includes this fix? 🙂

@Yadunund
Copy link
Member

Yadunund commented Apr 5, 2025

We are waiting to get #595 before doing a version bump and blooming a release.

What's most important before the freeze is getting source code merged into rolling. We can always bloom releases after. In fact, a new rolling version will be bloomed before we can branch to kilted anyways

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.

Unable to send 10 MB messages through the network
3 participants