You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dvc add --to-remote -r my-remote : breaks the tracked directories
Description
I have nightly runs running in CI (in my case github actions) where i collect new data and want to add them to a tracked directory. Running this in the CI-runner, it sets a limitation that we can't access the same cache we used while developing as it is .gitignored and I don't want to have any of the actual data in my git repository.
I managed to circumvent the cache hit by using the --to-remote flag but that causes some unexpected results in my tracked directory. The file is not added into the tracked directory and the tracked directory has been overwritten as a tracked "object"
Reproduce
Create azure storage
Track a directory
add files to tracked directory using --to-remote flag
Set up an azure storage container and initialize environment
Let's add more data and simulate the run in the CI
# To emulate the CI run, remove the cache from its original location
mv .dvc/cache /tmp/
printf"foo,bar\n1,2\n3,4">> data/raw/testdata/file2.csv
# Then circumvent the cache and push directly to remote
dvc add data/raw/testdata/file2.csv --to-remote -r my-remote
After this the tracked directory seems to be messed up
The tracked object is not double in size anymore as would be expected and the tracked object is no longer a directory
Bug Report
Issue name
dvc add --to-remote -r my-remote : breaks the tracked directories
Description
I have nightly runs running in CI (in my case github actions) where i collect new data and want to add them to a tracked directory. Running this in the CI-runner, it sets a limitation that we can't access the same cache we used while developing as it is .gitignored and I don't want to have any of the actual data in my git repository.
I managed to circumvent the cache hit by using the
--to-remote
flag but that causes some unexpected results in my tracked directory. The file is not added into the tracked directory and the tracked directory has been overwritten as a tracked "object"Reproduce
Set up an azure storage container and initialize environment
Adding the initial data and tracking the directory
The tracked directory should look like this
Let's add more data and simulate the run in the CI
After this the tracked directory seems to be messed up
The tracked object is not double in size anymore as would be expected and the tracked object is no longer a directory
Expected
I expect the tracked data size to be doubled and to be tracking 2 files in a tracked directory
Environment information
Azure Storage Account
Linux
dvc==3.55.2
Output of
dvc doctor
:Additional Information (if any):
The text was updated successfully, but these errors were encountered: