-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve TODO about Mac OS failing tests #268
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Address.resolve_ip
function and the async counterpart can now probably be removed completely, since they were only really relevant for UDP connections which required an IP, but that's no longer the case here.
I had the same idea. Seeing as how we just released those, maybe it's not too late to take those out from the public API without any deprecation period. |
4fbe334
to
37111bc
Compare
Any updates on this? |
37111bc
to
b544fbc
Compare
Thanks to 21fb8ce, able to remove these TODO comments. |
If it's done, could you please make it ready for review? |
Mac OS tests still failed in CI, and I haven't looked at why yet. |
The Failed run: Success run: Change between runs: |
Closing this stale work |
This actually applied to multiple operating systems, but required using a DNS server that answers to queries about localhost. Responding to those with anything but NXDOMAIN violates the DNS RFC, so it's surprising to see this be so rampant out in the wild. Anyway, the solution is to use
getaddrinfo
to let the OS stack handle resolution of names.