-
Notifications
You must be signed in to change notification settings - Fork 414
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
WARN Could not load all certificates - BadDER #1224
Comments
Thanks for reporting this. We switched the default our build system from openssl to rustls, but it wasn't entirely intentional to switch the Python package. I think we should switch back in the next version. If need be, I can do a bugfix release that switches back too. There are some workarounds for MacOS described here: rustls/rustls#127 (comment) Does that fix it for you? |
Thanks @wjones127, no need for bugfix release as it's not a severe issue. I don't want to touch the certs so it's fine with the warning. Just opened so you're aware of this. Thanks! |
# Description We changed default to make our workspace harmonious, but didn't mean to change this for the Python release. # Related Issue(s) - closes #1224 # Documentation <!--- Share links to useful documentation --->
…inux release This change enables the use of Rustls for the manylinux Python wheel, which was originally disabled in #1224. That issue was only affecting MacOS and has likely since been resolved. The switch from openssl motivated by the issue described in openssl/openssl#25367 Closes #2848
…inux release This change enables the use of Rustls for the manylinux Python wheel, which was originally disabled in #1224. That issue was only affecting MacOS and has likely since been resolved. The switch from openssl motivated by the issue described in openssl/openssl#25367 Closes #2848
Environment
Delta-rs version: 0.8.0
Binding: Python (3.10.8)
Environment:
Bug
What happened:
After upgrading to 0.8.0, all operations display the following warning:
Looks like deltalake is not able to load certificates in the native OSX truststore. I do have a few unsigned/self-signed certs in my truststore so that might be it, but in that case I'd expect a message saying it's not able to validate it, not "bad" cert.
What you expected to happen:
How to reproduce it:
More details:
The text was updated successfully, but these errors were encountered: