-
Notifications
You must be signed in to change notification settings - Fork 3
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
dvc pull from an s3 bucket fails with _init__() got an unexpected keyword argument 'ssl_verify' #40
Comments
Hi @JenniferHem , So what error are you getting? Please post full |
The full output is (redacted to not contain the user and urls):
|
@efiop If it helps: we also have a WebDAV backend which works without any issues. Just saw this for s3 |
and pulling data works with dvc version 2.8.3 (which was suggested by a colleague) |
@JenniferHem The error is clearly comming from http remote and not from s3 remote. Could you show |
remote.myremote.url=https://myremote.net:8080/myremote |
@JenniferHem Thanks. Btw, when you are saying Regarding the error itself, could you also run |
pip check pip freeze I cannot really tell you what the underlying technology is we are using sorry. Just that its not an AWS bucket. |
We have the same issue and we work with a http-remote and we add the ssl_verify option to False https://dvc.org/doc/command-reference/remote/modify#http DVC VERSION: 2.41.1 Checked with DVC 2.38.1 and works fine! This is the .dvc/config
|
Seems to be related to https://github.com/iterative/dvc-http/pull/28/files , i see that we've changed some logic there. Moving to dvc-http |
Fixed by #32 Will be part of the next dvc release later today. |
Bug Report
Description
My remote is an s3-like bucket which needs ssl verification, however running dvc pull with the config containing ssl_verify=/path/to/cert results in the abovementioned error.
Expected
dvc pulls the data
Environment information
Output of
dvc doctor
:Additional Information (if any):
The text was updated successfully, but these errors were encountered: