When there are file creation/deletion conflicts, write backup files to disk
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 54
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 3
Description
Example: Two peers created file "file" while not connected. Then they connect.
Currently, one version would be overwritten.
Solution might be to save a backup of the overwritten version "file.2" or something.
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
No source file or test is named. Start by tracing the file synchronization path for conflicts between concurrently created files, then determine how the overwritten version is currently discarded. Done means the losing version is preserved on disk under a deterministic backup name such as "file.2", with coverage for the two-peer creation scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100