Use nc command if it exists and specify explicit connection timeout to avoid hanging #109
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.
Use nc command if it exists.
Add explicit connection timeout of 10 seconds, because, depending on the system, nc command could be a symlink to netcat or Ncat program (a netcat re-implementation), and Ncat has a default connection timeout od 10 seconds (thus this value was chosen), while netcat has infinite connection timeout by default. Infinite connection timeout resulted in wait-for-it.sh to hang and never succeed to connect to target host if it wasn't reachable initially but became reachable a bit later (for example when starting docker containers), until main wait-for-it.sh timeout expired, at which point it is too late.
The same timeout value of 10 seconds is also added to network redirection for the same reason.