microsoft / microsoft/VFSForGit
`gvfs clone` has an exit code of 0 when the "Mounting..." step fails due to BrokenPipeException
Open
Nobody has claimed this yet.
type: bug
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
This seems like it could be a bug, consider returning a specific error code that indicates the clone succeed but mount failed.
It's possible (but I think probably doubtful) that 0 is returned here because the clone did, in fact, succeed.
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 gvfs clone command to the "Mounting..." step and locate where BrokenPipeException is handled. Reproduce the failure if possible and inspect the current exit-code path. Done means a failed mount after a successful clone returns a distinct nonzero exit code, with coverage for that scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100