-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 push: Unexpected error when pushing to Google Cloud storage or S3 #10206
Comments
Looks like we are accidentally trying to push to that import-url's fs. Taking a look... |
Ok, with index migration we need |
Is it about read-only? Or, is it about traversable/non-traversable remotes? Our implementation of |
@skshetry We are trying to push to http that we've import-url-ed from and which is not even set up as a remote, so the former. |
@turkanis Could you try upstream dvc, please? https://dvc.org/doc/install/pre-release Should be fixed now. |
Thanks for your quick response. With the pre-release version, I no longer get an error when I run
Is this the expected behavior? It is not what I expected. If, instead, I add the To summarize, without --to-remote, the file is copied to the project directory, a .dvc tracking file is created, but the data never gets written to remote storage. Running |
@turkanis If you've pushed already and there are no new files to push then it is expected that it is not pushing anything.
|
In the scenario I described, I had never pushed before, and there were no objects in remote storage. |
I think I have not described the situation well. Here are the 2 scenarios that occur. In both cases, some of the behavior seems wrong to me. Both start out with nothing in remote storage: Scenario I
Scenario II
Is this expected behavior? What I want is the imported file to be written to remote storage and to have a .gitignore entry created automatically. Thanks for your help! |
Bug Report
dvc push: "Unexpected error" when pushing to Google Cloud storage or S3
Reproduce
output (s3):
output (gcs):
Expected
Successful push
Environment information
Additional Information (if any):
The text was updated successfully, but these errors were encountered: