Tomoya Fujita

> Knowing the IP address, I could directly identify and log-in to the offending host and adjust the ROS_DOMAIN_ID settings there. Without it, I would need to try all the...

> The error unknown goal response, ignoring... is relatively new, introduced in #2132. CC @fujitatomoya https://github.com/ros2/rclcpp/pull/2132 is merged in before `Iron` release, so this has been a while up to...

how about merging bag files into one via `ros2 bag convert -i xxx -i yyy -o zzz.yaml` and the use it with `ros2 bag play zzz`? see more details for...

@tonynajjar thanks for creating issue. so are you suggesting using `--ros-args --log-level minimal_action_server:=debug` only sets the logging debug level to `minimal_action_server`? not all subordinate child loggers, right?

How about the following? does that work for you? ```bash root@tomoyafujita:~/ros2_ws/colcon_ws# ros2 run examples_rclpy_minimal_action_server server --ros-args --log-level minimal_action_server:=debug --log-level minimal_action_server.action_server:=WARN [INFO] [1676571229.724406498] [minimal_action_server]: Received goal request [INFO] [1676571229.725345312] [minimal_action_server]: Executing...

IMO, - i think current logger hierarchy is not bad design, if the logger level is unset, walks up to hierarchy to find and set the logger level. (this is...

> One thing that would be very nice here is to have a rqt tool that allowed you to introspect the entire logging hierarchy, and then selectively enable/disable the loggers...

This feature sounds interesting, but we surely need to consider more details for implementation note and suggestions. i believe that [REP](https://github.com/ros-infrastructure/rep) would be the good way to start the more...

@adityapande-1995 out of curiosity, > When using other build systems like bazel, there may not be a ament prefix path bazel is officially supported? there are many build tools...

@beetleskin LGTM