Add waiting for RPC server to become available #331
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wouter-heerwegh
approved these changes
Sep 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've encountered an issue where if the ros bridge and the simulator are launched simultaneously, but the simulator takes longer to load, then ros bridge exits with an error saying that it could not connect. I thought that it would be better to wait a configurable amount of time for the simulator to load, so I've added this to the ROS2 bridge. @wouter-heerwegh, could you copy and test the changes for ROS1? Should be quick, the change is really small.
The ROS parameter
timeoutwill control how much time to wait for the RPC server (simulator) to become available