Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This seemingly minor change fixes pushing data to an HTTP remote storage with
dvc
v2.16.0. At the moment,dvc
v2.16.0 cannot push any data at all to an HTTP remote storage!I noticed that with
dvc
v2.15.0 pushing data to an HTTP remote storage works fine while it doesn't work - i.e. data just isn't transferred without an error - with v2.16.0. Betweendvc
v2.15.0 and v2.16.0,dvc-objects
(a transitive dependency ofdvc
viadvc-data
) was bumped from v0.1.5 to v0.1.6 by the bump ofdvc-data
from v0.1.5 to v0.1.6. After some digging, I arrived atdvc-objects
and #114 which, among other changes, changed the implementation of theObjectDB.exists(...)
method:Now,
FileSystem.exists(...)
simply delegates the call to the underlyingfsspec
filesystem implementation, butHTTPFileSystem.isfile(...)
overrides this delegation by a hardcoded return valueTrue
which makes theObjectDB.exists(...)
method always returnTrue
and prevents any data upload to an HTTP remote storage because every file is considered to exist already.