When connectionTimeout is not configured, await() gets into a spin-loop.

[arunmk]

I have a configuration where the connectTimeout is missing. In that case I get 1000s of attempts to connect.

Excerpt without connectTimeout:
[Error: connection timeout] Attempt 1 timed out. Time elapsed: 10.354 ms
.
.
.
[Error: connection timeout] Attempt 6647 timed out. Time elapsed: 15.234 s
[Error: connection timeout] Attempt 6648 timed out. Time elapsed: 15.236 s
[Error: connection timeout] Attempt 6649 timed out. Time elapsed: 15.237 s
[Error: connection timeout] Attempt 6650 timed out. Time elapsed: 15.240 s
[Error: connection timeout] Attempt 6651 timed out. Time elapsed: 15.241 s
Connected. Running test query: 'SELECT 1'
Query done.
Query succeeded after 6652 attempt(s) over 15.252 s

Excerpt with connectTimeout:250 specified in the config:
Connected. Running test query: 'SELECT 1'
Query done.
Query succeeded after 1 attempt(s) over 21.804 ms

Since the default is 250, I would expect the behavior to be identical. I will need to check the code in a while as to the root-cause.

[arunmk]

I found the error. It is that the runScript() sets default values while the await() function that we use does not set default values.
@joeledwards, could you please comment if that is the intentional behavior? I would expect there to be some default value if none are specified.

[arunmk]

Possible fix where await() and runScript() use the same defaults at: #5

[joeledwards]

Let me know if the updated version (1.5.1) resolves the issue.