Skip to content
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

Align the default QoS with other RMWs #485

Open
YuanYuYuan opened this issue Feb 27, 2025 · 0 comments
Open

Align the default QoS with other RMWs #485

YuanYuYuan opened this issue Feb 27, 2025 · 0 comments
Assignees

Comments

@YuanYuYuan
Copy link
Contributor

YuanYuYuan commented Feb 27, 2025

The following table summarizes the default QoS of the popular RMWs.

QoS Policy rmw_cyclonedds_cpp rmw_zenoh rmw_fastrtps_cpp
History Keep Last (Depth = 1) Keep Last (Depth = 42) Keep Last (Depth = 1)
Reliability Reliable Reliable Best Effort
Durability Volatile Transient Local Volatile
Lifespan Infinite (if unspecified) Infinite Infinite
Deadline Infinite (if unspecified) Infinite Infinite
Liveliness Automatic Automatic Automatic
Liveliness Lease Duration Infinite (if unspecified) Infinite Infinite

The question is why we use Transient Local by default. This different QoS setting causes the failure at nav2_behavior_tree/test/plugins/condition/test_is_battery_low. Since navigation2 simply uses the default QoS in the test and expect the durability is volatile.

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

No branches or pull requests

2 participants