libgit2 / libgit2/libgit2sharp
Network.Fetch can fail in some cases
Open
Nobody has claimed this yet.
Up for grabs
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
Looking over the Network.Fetch code, I think that it can fail in some specific scenarios:
If you load a Remote from a Repository, and it gets deleted by an external process in the time before being passed to Network.Fetch, Network.Fetch will try to reload it from the repository and fail.
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 at Network.Fetch and trace how a Remote loaded from a Repository is reloaded before the fetch. Reproduce the deletion race described in the issue, then add coverage for that scenario and verify the resulting behavior without relying on the removed Remote.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100