Error: failed to lookup address information: nodename nor servname provided, or not known

[Czino]

          @BitcoinZavior yes, I am already using `concurrency` to speed things up a little

Originally posted by @Czino in #44 (comment)

Having set concurrency to just to 5 I noticed that in some instances the following error is thrown when a user calls the sync method around 5 times at the same time. (i.e. concurrency >= 25)

failed to lookup address information: nodename nor servname provided, or not known

After some digging I found the following explanation which is why I think concurrency might be the culprit behind

Wanted to take a note here, in case someone else hits this error and comes looking for it. Not sure if the issue should may be raised in the bdk/bdk-ffi repo

[Czino]

Increasing concurrency also has other unstable side effects.

• timed out reading response
• tls connection init failed / AlertReceived(HandshakeFailure)
• ConnectionAborted / Software caused connection abort

After reducing concurrency to 2, the errors seem to disappear