Closed johnnyhh closed 6 years ago
"thumbs up" means "I'm affected by this as well" :-)
I'm sorry about this.
There should be updated gems for both async-io
and async-dns
which resolve this problem.
I will review the issue and report back.
It's my fault. My apologies. I prepared but forgot to release async-dns v1.1.0
. I've now done this and everything is working as expected. Make sure you are using async-io ~> 1.3
and async-dns ~> 1.1
.
By the way, this kind of issue should't happen again as the endpoint API is much more stable now.