-
Notifications
You must be signed in to change notification settings - Fork 1.3k
dvc: refactor cache/remote relations #4867
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
Conversation
dvc/cache/base.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previosly we checked the index here, but that was mixing up remotes and caches, which is incorrect, so now we first check the index in Remote(because our current indexes are local indexes for remote caches) and then fallback to checking cache, which is naturual and provides nice intuitive isolation.
dvc/remote/__init__.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We never needed an SSHRemote, as all of the custom stuff was actually about SSHCache.
dvc/remote/base.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This conversion that we do might be causing things like #4139 . Might want to check.
…limit * 'master' of github.com:iterative/dvc: dvc: refactor cache/remote relations (treeverse#4867) codecov: add target coverage, and threshold for patch and project (treeverse#4873)
The final separation that puts this Cache/Remote/Tree trio in their proper places.
No new logic added, just tossing around methods to make them lend in logical places (except for minor gc message adjustments and new internal helpers). E.g. index is for Remote, but listing the cache is for Cache.
❗ I have followed the Contributing to DVC checklist.
📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏