microsoft / microsoft/VFSForGit
Provide clear message/instructions if 'gvfs sparse' fails mid-command
Open
Nobody has claimed this yet.
domain: sparse
pri2
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
See discussion here: https://github.com/microsoft/VFSForGit/pull/1605#discussion_r349820391
If gvfs sparse has a failure doing one of its steps (e.g. dehydrating) make sure that the error is surfaced clearly to the user and that they're provided with actionable steps.
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 discussion on pull request 1605 and trace the gvfs sparse steps, especially dehydration. Reproduce a mid-command failure and identify where the error is surfaced; done means the user receives a clear failure message and actionable recovery instructions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100