Tomoya Fujita

Just FYI, this does not happen Linux platform. ros2 doctor --report on Linux / Galactic Binary Release ``` root@263f0153ac57:~# ros2 doctor --report NETWORK CONFIGURATION inet : 172.17.0.4 inet4 : ['172.17.0.4']...

This does not happen with https://github.com/ros2/ros2/commit/5a35507c37f3b0449e31cb4073cf0352bfd52b0b ```bash root@tomoyafujita:~/ros2_ws/colcon_ws# ros2 node info /minimal_publisher /minimal_publisher Subscribers: /sub: std_msgs/msg/String Publishers: /parameter_events: rcl_interfaces/msg/ParameterEvent /pub: std_msgs/msg/String /rosout: rcl_interfaces/msg/Log Service Servers: /minimal_publisher/describe_parameters: rcl_interfaces/srv/DescribeParameters /minimal_publisher/get_parameter_types: rcl_interfaces/srv/GetParameterTypes /minimal_publisher/get_parameters:...

I confirmed that this cannot be observed in humble or rolling, and https://github.com/ros2/ros2/issues/1301#issuecomment-1197864161 makes that this is the problem for foxy only. > I immediately see service response on first...

Thanks for checking. I think there have been many fixes during galactic for `rmw_fastrtps`. @MiguelCompany @iuhilnehc-ynos any idea what could be related to this issue?

Just FYI, https://github.com/eProsima/Fast-DDS/pull/2906 backport is under review.

This has been addressed. @clalancette can you close this?

@chenyongmin1 i am not sure what the problem here, could you explain a little bit more, like you can see the topics which are not supposed to exist? or redundant...

So the application will read and understand the error message and make the next action? I am not sure how many application takes advantage of this error messages... what if...

@gavanderhoorn sorry for the confusion. > How would an action client know why its goal was rejected? adding implementation specific messages could help, at least we can log the reason...

yeah, i understand what you asking for here. ultimately everything can be up to user, as framework just define byte fields, and we can say user can do whatever they...