From 4c6e4130f962a8c717108bd48669b7a7ddd2a26f Mon Sep 17 00:00:00 2001 From: "Felix Exner (fexner)" Date: Fri, 25 Oct 2024 15:18:23 +0200 Subject: [PATCH] Fix timeout value in std output (#1807) We were using the wrong timeout in the terminal output there. (cherry picked from commit cb91599f8f66aaf39b7485a2f7e131157f633474) # Conflicts: # controller_manager/controller_manager/controller_manager_services.py --- .../controller_manager/controller_manager_services.py | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/controller_manager/controller_manager/controller_manager_services.py b/controller_manager/controller_manager/controller_manager_services.py index 25cd932dab..6a4e61c747 100644 --- a/controller_manager/controller_manager/controller_manager_services.py +++ b/controller_manager/controller_manager/controller_manager_services.py @@ -105,8 +105,13 @@ def service_caller( rclpy.spin_until_future_complete(node, future, timeout_sec=call_timeout) if future.result() is None: node.get_logger().warning( +<<<<<<< HEAD f"Failed getting a result from calling {service_name} in " f"{service_timeout}. (Attempt {attempt+1} of {max_attempts}.)" +======= + f"Failed getting a result from calling {fully_qualified_service_name} in " + f"{call_timeout}. (Attempt {attempt+1} of {max_attempts}.)" +>>>>>>> cb91599 (Fix timeout value in std output (#1807)) ) else: return future.result()