dsync --delete --contents tries to compare content even on files that don't exist in src
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 200
- Forks
- 85
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 2
Description
A dsync --delete --contents tries to compare content on file that doesn't exist in src.
source:
/a/d1/f01
target:
/b/d1/f01
/b/d1/f02
dsync --delete --contents /a/d1 /b/d1
tries to do a content compare on /a/d1/f02 with /b/d1/f02, but since --delete is set it should just remove the file regardless of content.
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 dsync implementation for the --delete and --contents options, using the /a/d1 and /b/d1 example to reproduce the behavior. Check the handling of target-only files such as f02 when the source path is absent. Done means dsync --delete --contents removes the target-only file without attempting a content comparison.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100