microsoft / microsoft/VFSForGit
Make sure that we can separate time spent in GVFS.Hooks.exe from time spent in other post-command hooks
Open
Nobody has claimed this yet.
affects: live-site
domain: sparse
pri2
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
This will help understand the impact of post-command hooks other than VFS4G's 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 locating the existing post-command hook timing and reporting around GVFS.Hooks.exe and VFS4G's hook. Determine how the measurement distinguishes GVFS.Hooks.exe from other post-command hooks; done means the resulting data reports those durations separately so their impact can be compared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- observability, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100