h-vetinari commented on issue #38280: URL: https://github.com/apache/arrow/issues/38280#issuecomment-1765521928
Thanks for the ping. We continuously rebuild arrow (and many other packages) for new versions of underlying packages, including grpc & protobuf, most recently for grpc 1.58.1 & protobuf 4.24.3. This happened across all maintenance branches (v10-v13), so if the problem/bug is related to grpc 1.58, you'll get it on arrow 12 as well. Though, to be honest, "Could not contact DNS servers" sounds like a connectivity issue; I'm not sure if the URL `server-address.us-east-1.elb.amazonaws.com:8815` has been obfuscated for privacy (it's not reachable for me, also without the port number), but given the AWS-context, it sounds quite plausible to me that there could be an issue around accessing a private resource in the cloud, e.g. because the environment where arrow is running does not have the right credentials / tokens or is not in the right VPN. In any case, short of a more concrete bug report (e.g. a reproducer or better: a test case; alternatively some issue reference in grpc, or other affected third-party software) there's not much we in conda-forge can do. We run the full pyarrow test suite before publishing packages, so from that POV, the packages are fully functional (as much as we can reasonably assure). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
