Tomoya Fujita

i think that because you are trying to build `rclcpp` without `rclcpp` test dependent packages. can you try with, ```bash colcon build --packages-up-to rclcpp rclcpp_action rclcpp_components rclcpp_lifecycle ```

yeah, i think it is nice to have. the following is output from `rostopic hz` from ROS 1 just a reference. ```bash root@4b5f2b7e1de8:~# rostopic hz /chatter /rosout subscribed to [/chatter]...

i think @iuhilnehc-ynos created https://github.com/ros2/ros2cli/pull/831 already. it would be nice if you can do review for that 👍

@tompe17 could you address DCO error https://github.com/ros2/ros1_bridge/pull/347/checks?check_run_id=5623872538 ?

CC: @iuhilnehc-ynos

Reference: https://github.com/NVIDIA/k8s-device-plugin

sounds good to me.

> This adds up to 10+ builtin topics per node, most of which are never used, and can bog down a network with discovery traffic on application startup. totally agree...

> I think "lazy client" doesn't make sense - just like "lazy subscriber". The concept should probably limit to data producers/service providers (action servers?) agree :+1: > Maybe we could...

> graph guard condition exposed in Python, and > something like "get service clients info by service name" in rmw, rclcpp, and rclpy sounds good to me. > Services version...