Just glanced at the issue, looks like you summarized it well.
On 1/23/24 12:58 PM, Nicholas Chammas wrote:
To close the loop on this discussion, I’ve filed the following issue
with the gRPC folks:
https://github.com/grpc/grpc/issues/35638
Thank you again for all of your help. I would not
To close the loop on this discussion, I’ve filed the following issue with the
gRPC folks:
https://github.com/grpc/grpc/issues/35638
Thank you again for all of your help. I would not have been able to understand
what’s going on without it.
> On Jan 23, 2024, at 11:43 AM, Brad House wrote:
>
Yeah, it does clearly show them enqueuing IPv4 and IPv6 requests
separately. So either they need to add logic similar to c-ares has
internally with https://github.com/c-ares/c-ares/pull/551 or just use
ares_getaddrinfo() instead of ares_gethostbyname() with address family
AF_UNSPEC and let
Thank you for all the troubleshooting help, Brad.
I am using gRPC via Apache Spark Connect (a Python library), so I am two levels
removed from c-ares itself. Looking in the Python virtual environment where
gRPC is installed, I’m not sure what file to run otool on. The only seemingly
relevant
