Self update could interfere with itself
Open
Nobody has claimed this yet.
A-concurrency
enhancement
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
We don't seem to download the self-update to a unique pathname. As such two self-updates could interfere with one another.
It probably makes sense to alter the self-update pathways to use unique names and potentially to use a lockfile during the actual update process after download.
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 tracing the self-update pathways, focusing on where the update is downloaded and where the actual update process begins. Confirm how concurrent self-updates can share a pathname, then define completion as unique download names and safe serialization of the update process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100