RAR cache dirty reason should be logged
Open
Area: Debuggability
Area: Logging
triaged
- Dominant language
- C#
- Stars
- 5.5k
- Forks
- 1.5k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 133
Description
RAR should log the reason why the state file became dirty and why it chose to write it. It's hard to diagnose why the state file is written every time on empty rebuilds where nothing changes.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the RAR cache logic that marks the state file dirty and decides to write it, then inspect how empty rebuilds reach that path. Reproduce an empty rebuild and identify the existing diagnostics around the decision. Done means the logs explain why the state became dirty and why the file was written.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100