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

Items to finish before Jazzy release #110

Closed
clalancette opened this issue Feb 14, 2024 · 2 comments
Closed

Items to finish before Jazzy release #110

clalancette opened this issue Feb 14, 2024 · 2 comments
Assignees

Comments

@clalancette
Copy link
Collaborator

clalancette commented Feb 14, 2024

This issue puts together the list of items, in rough priority order, that should be completed on rmw_zenoh_cpp before Jazzy. Not all of these are strictly required, as basic functionality is already there, but having all of these will go a long way towards making rmw_zenoh_cpp something that people can actively try out.

Status Item Why? Related issues/PRs
Complete Events support Required for rviz2, ros2 topic, and other tools #103
Complete Build rmw_zenoh_cpp on Ubuntu 24.04 with rustc on that OS Will be necessary to tell users how to use rmw_zenoh #136
Complete Implement rmw_take_serialized_message{_with_info} Required for rosbag2 #113
Complete Implement rmw_get_gid_for_client Required to support service introspection #115
Complete Implement rmw_get_gid_for_publisher We are currently lying to the upper levels, so should fix that #116
Not started Implement rmw_publisher_wait_for_all_acked Required to support rclcpp/rclpy wait_for_all_acked, used in tests
Complete Allow the user to pass a custom config file to init_rmw_zenoh_router User customization of zenohd will be important #119
Complete Fill in the source timestamp and GID for published messages End-users expect this information to be there #123
Not started Restrict Zenoh sessions/router to a specific network interface Important for certain use cases, like Velodyne sensors which use ethernet
Complete Run rmw_zenoh_cpp against all tests in the ROS 2 core This will give us much more confidence in the things we have implemented, and show us weaknesses #162, #161, #156, #154, #151
Complete Revisit how and when to start the zenoh router; should we do it all, should we do it automatically, or should we make the user do it? Starting it automatically makes it more seamless, but gives the user less opportunity to configure. Need to consider the tradeoffs and what the default should be #135
@ros-discourse
Copy link

This issue has been mentioned on ROS Discourse. There might be relevant details there:

https://discourse.ros.org/t/ros-2-meeting-minutes-2024-02-15/36221/1

@Yadunund Yadunund pinned this issue Feb 27, 2024
@clalancette clalancette self-assigned this Apr 4, 2024
@clalancette
Copy link
Collaborator Author

Closing this one out, as we are post-Jazzy and working on other parts of rmw_zenoh_cpp now.

@clalancette clalancette unpinned this issue Jul 1, 2024
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