Extend status -c command to also check for corrupted files on the remote
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.9k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
See discussion on Discord here.
In short, we experienced corrupted files on our google cloud storage when using DVC.
See #7268 for more details.
When this situation occurs it would be convenient to have the dvc status -c to also check for corrupted files.
In our case, we could use gsutil ls -L to list the bas64-encoded sha values for all files in our bucket and compare that to the md5 file names given to the files by DVC.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the dvc status -c command and review issue #7268 plus the linked Discord discussion for the corruption scenario. Determine how remote file checks currently work and how gsutil ls -L exposes hashes; done should include detecting and reporting remote files whose content hash differs from the DVC filename.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100