Use bulk calls for checking which entries are not in remote #10923
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
skshetry
reviewed
Dec 10, 2025
skshetry
reviewed
Dec 10, 2025
This also removes the general `except` block and uses fail-closed behavior for missing entries.
falko17
force-pushed
the
feature/bulk-remote-exists
branch
from
1867a64 to
f62458c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 uses the new
bulk_remote_existsfunctionality introduced in treeverse/dvc-data#637 for checking which entries are not present in the remote (e.g., duringdvc data status --not-in-remote).This is a draft for now until that PR in dvc-data is merged.