microsoft / microsoft/VFSForGit
gvfs mount fails after changing the repo drive letter
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
Customer report-
After changing the drive letter of my disk partition where my Git+GVFS repo is located, GVFS continues to look for the .gvfsCache folder under my old drive letter. Is there a way to reconfigure it?
In the following snippet, Z: is my new drive letter, and D: the old.
Z:\git\Substrate\src>gvfs mount
Authenticating...Succeeded
Querying remote for config...Succeeded
Configured cache server: User Defined (https://ossgvfs.redmond.corp.microsoft.com/ee6fb219f8924d029e965c16fe59c175)
Failed to create local cache: D:.gvfsCache
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 reproducing gvfs mount after changing the repository drive letter and trace how the local cache path is selected. Verify whether the old drive letter is stored or derived during mounting. Done means mounting uses the current drive letter or provides a supported way to reconfigure the cache location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100