microsoft / microsoft/VFSForGit
Some unsupported Git commands take GVFSLock
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
Some git commands are unsupported in virtualized (VFS4G) repositories, and git will return an error when they are run inside of a virtualized repository. Depending on the type of command, git might block execution before or after calling the pre-command hook. If this command results in the GVFSLock being acquired, this can affect other actions, such as placeholder creation.
Is it possible for Git to block all "unsupported" commands before running the pre-command hook?
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 an unsupported Git command inside a virtualized VFS4G repository and observe when the pre-command hook and GVFSLock are involved. Trace the command-blocking and hook order, then verify that unsupported commands are rejected before the hook and do not acquire GVFSLock.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- devtools, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100