Tomoya Fujita

> Basically, I installed ros2-humble on a remote server, and I installed and ran turtlebot3 and moveit2. However, after I killed moveit2 and turtlebot (I use ps aux to ensure...

I will go ahead to close this since weavenet is E.O.L

@SteveMacenski @clalancette @AlexeyMerzlyakov what do you think?

> last-updated time? last-result-requested time? i see, maybe we can rely on server process or event that resets the timeout. (e.g `publish_feedback`, `publish_status` or `result_request_received`) thanks for the idea. the...

@sloretz thank you for sharing comments. I might be mistaken, so i need to check. > The expire timeout is being calculated from the time the goal was accepted. It...

@iuhilnehc-ynos @Barry-Xu-2018 could you check this when you have time? i would like to have the 2nd opinion. thanks in advance.

@Barry-Xu-2018 @iuhilnehc-ynos you guys have bandwidth for this fix? that would be really appreciated. CC: @clalancette @sloretz

> While the timeout is set to 0, make sure that users always receive the goal result. i am not really sure about this comment. https://design.ros2.org/articles/actions.html#result-caching explains well. > If...

Understood. there will be always racy condition between `result requested` and `goal completed` in this case. I think that is why we have own timeout option that server can manage...

btw, > If the timeout is configured to have value -1 i guess, we would take this as `if negative` with `typedef int64_t rcutils_duration_value_t;`. we can check `-1`, but what...