microsoft / microsoft/VFSForGit
Introduce some kind of log rotation / retention policy
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
Currently, a single log file is used for the entire lifetime of GVFS.Mount (which ideally is a long time). Perhaps introducing a log rotation policy, where a log file is changed weekly or daily would make the log analysis easier?
Also, if the user uses a single GVFS enlistment for months and the runs gvfs diagnose, that package will include all the log files, that ever existed, which is not always necessary.
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 how GVFS.Mount creates and retains its log file, then inspect how gvfs diagnose packages logs. Define a daily or weekly rotation policy and ensure diagnosis does not include unnecessary historical logs; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100