This is an awkward bug to report, as I’m unable to reproduce it with a toy example (despite creating some repos just for that purpose), and cannot share the original bug, as it happens in private repos.
Perhaps it’s some configuration weirdness on my end - hence a forum post.
When using dvc>=2, upon running
dvc pull (also
dvc pull -R and similar), files that are
dvc import-ed from other repos don’t actually get pulled.
dvc immediately returns with
Everything is up to date, without even cloning the repos that we should import from.
The only way to pull the files seems to be specifying each file individually -
dvc pull some_dir/some_file.dvc.
dvc<2 in the same repos - everything gets pulled.
Note: this behavior is consistent for all of my teammates, in several different repos. Tested on Ubuntu and Mac. Effectively it stops us from upgrading to dvc v2, as we heavily rely on
A couple of facts that might be relevant:
- we usually have multiple DVC repos per git repo, in sub-directories
- we’re using S3 and sometimes “local” remotes (the latter refer to different DVC repos in the same git repo)
I would really appreciate any suggestions for how to investigate further. As mentioned, simple imports in toy repos seem to work fine.
Thanks a lot!