The previous wait time was very short, and I believe it was being
detected as port scanning. This increases that time and makes it a
kwarg so it is configurable in the event a user needs a short wait time.
I tested this, and it seems to work, OK. It blocked until TCP was available
on my node, where before I found this function would stay blocked.
Looking at the code and testing more, I'm not sure why this fixes anything.
create_connection has its own timeout, like ~60 seconds, and then
the sleep kicks in. Perhaps the firewall was upset that connection was being
reopened so soon?
The previous wait time was very short, and I believe it was being detected as port scanning. This increases that time and makes it a kwarg so it is configurable in the event a user needs a short wait time.
I tested this, and it seems to work, OK. It blocked until TCP was available on my node, where before I found this function would stay blocked.
Looking at the code and testing more, I'm not sure why this fixes anything.
create_connectionhas its own timeout, like ~60 seconds, and then the sleep kicks in. Perhaps the firewall was upset that connection was being reopened so soon?