dcmp: add checkpointing with file batches
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 200
- Forks
- 85
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 2
Description
For long running dcmp jobs, it would be useful to checkpoint the state.
It may be possible to do this by batching files, as with dsync. In this case, we'd write out the file list for both the source and destination. We'd have to write out the current status of any checks (the list of matching files, and perhaps the check itself). We'd also need to record a marker of how far we are along in the source/destination lists.
We'd want to take a path from the user where this checkpoint data could be saved, and then take that path again on a restart.
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 by reading the dcmp implementation and the existing dsync file-batching behavior. Trace how source and destination file lists, check status, and progress are handled. Done means checkpoint data can be saved to a user-provided path and reused to restart a long-running dcmp job.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100