Tomoya Fujita

@Mergifyio rebase

Pulls: ros2/ros2cli#916, ros2/rmw#371, ros2/rmw_implementation#238, ros2/rmw_fastrtps#771, ros2/rmw_cyclonedds#499, ros2/rmw_connextdds#154, ros2/rcl#1161, ros2/rclcpp#2569, ros2/rclpy#1307, ros2/rmw_dds_common#82, ros2/rmw_zenoh#679 Gist: https://gist.githubusercontent.com/fujitatomoya/01385d70469b48f205a68e21219fd395/raw/b02c84fd17938124e2b045dbf016f260e6209ae0/ros2.repos BUILD args: --packages-above-and-dependencies rmw_zenoh_cpp rmw_dds_common rclpy rclcpp_lifecycle rclcpp rcl rmw_connextdds rmw_connextdds_common rmw_connextddsmicro rmw_cyclonedds_cpp rmw_fastrtps_cpp rmw_fastrtps_dynamic_cpp rmw_fastrtps_sharedcpp...

Pulls: ros2/ros2cli#916, ros2/rmw#371, ros2/rmw_implementation#238, ros2/rmw_fastrtps#771, ros2/rmw_cyclonedds#499, ros2/rmw_connextdds#154, ros2/rcl#1161, ros2/rclcpp#2569, ros2/rclpy#1307, ros2/rmw_dds_common#82, ros2/rmw_zenoh#679 Gist: https://gist.githubusercontent.com/fujitatomoya/3c50929d3b3e884ba6796f6c9f26e92e/raw/b02c84fd17938124e2b045dbf016f260e6209ae0/ros2.repos BUILD args: --packages-above-and-dependencies rmw_zenoh_cpp rmw_dds_common rclpy rclcpp_lifecycle rclcpp rcl rmw_connextdds rmw_connextdds_common rmw_connextddsmicro rmw_cyclonedds_cpp rmw_fastrtps_cpp rmw_fastrtps_dynamic_cpp rmw_fastrtps_shared_cpp...

i think this can be resolved with https://github.com/ros2/rclpy/pull/1171, default value is way too big...

@holesond you are welcome. > A ten second long result_timeout may still be too long for larger request or response payloads such as images. https://github.com/ros2/rclpy/pull/1171 changes default timeout, you can...

@navaneeth-dev @wbc6080 sorry to be late to get back to you, i will take a look today.

Currently `TimeSource` is managed under `Node` object, so that clock subscription entity can be created to support simulation time for each `Node` object. (some nodes use simulation time, some do...

> If a node "fails", in a composed application, wouldn't the whole application fail too? you mean more like crashed by `fails`? if so, yes. composed nodes are in the...

i tried with `jazzy`, the following is what i see.  ```bash root@tomoyafujita:~# ros2 topic list /chatter /parameter_events /rosout root@tomoyafujita:~# ros2 service list /listener/describe_parameters /listener/get_parameter_types /listener/get_parameters /listener/get_type_description /listener/list_parameters /listener/set_parameters /listener/set_parameters_atomically...

i think this is reasonable, currently too strict. the directory must not exist. i think directory can exist but it needs to be empty or `metadata.yaml` is not there?