Closed MiguelCompany closed 1 year ago
If i understand correctly, this could be work-around to suppress the following issues.
CC: @MiguelCompany
If i understand correctly, this could be work-around to suppress the following issues.
@fujitatomoya Correct. Nonetheless, we still think the timeout should be handled in the upper layers.
lgtm
I just pushed a commit fixing the linters, so this is ready for a CI
@MiguelCompany @EduPonz can we backport this to iron and humble? that would be really useful.
can we backport this to iron and humble? that would be really useful.
@fujitatomoya Sure.
https://ci.ros2.org/job/ci_windows/20001/ is not related to this PR.
either @Barry-Xu-2018 or @iuhilnehc-ynos can you review this? i would like to have the another review for this.
@Barry-Xu-2018 @iuhilnehc-ynos friendly ping.
LGTM
@Mergifyio backport humble iron
backport humble iron
This pull request has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/need-help-with-client-will-not-receive-response/40849/1
This PR enables using the XML profiles to set the maximum time to wait for the client response reader to be ready when sending a response from the service.
It will use the value from the
max_blocking_time
tag, for which the default value is 100ms.The following XML would set the timeout to 1 second for all services: