microsoft / microsoft/VFSForGit
Kext log messages should include an ID that can be used to associate the log message with a mount process
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
For log messages that are repo-specific, the kext should include an ID (perhaps VirtualizationRootHandle?) that can be tied to the mount process for that repo.
Whatever ID is used will also have to be provided to the mount process when it registers/starts the virtualization root and the mount process will need to log it.
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 kext's repo-specific log messages and the mount process paths that register or start a virtualization root. Determine an ID that is available to both sides and can associate each log message with its mount process, then verify that the ID is included consistently in kext and mount-process logging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100