Closed stackotter closed 2 years ago
The only version I have produced this on is 6f3b01d (I haven't tried any other versions)
The only bug I get when attempting to join the test server is #67
It is possible that it was a DNS issue on my side or a temporary one for the test server. I'll try connecting again tomorrow. Because I am pretty sure that I touched nothing that would break DNS resolution. However, it would probably be a good idea to set a timeout for DNS resolution.
Hasn't ever happened again. I'm gonna close this
Steps to reproduce
Details
It seems to be a deadlock that occurs when resolving the SRV records, so the server host may have changed how they use SRV records. I think it could possibly be a bug in NioDNS (the library I am using to resolve SRV records), but I would have to look into it further to be sure.