AcademySoftwareFoundation / AcademySoftwareFoundation/rez
add optional 'touched packages' metric to resolves
Open
enhancement
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 374
- Avg merge
- 9d 12h
- Merged PRs (30d)
- 5
Description
It would be useful to know what packages were considered during a resolve. This should help identify issues where iterations back to old versions causes slow resolves
Contributor guide
Research direction
No file or test is named. Start by locating the resolve implementation and any existing metrics, then determine how an optional touched-packages metric should expose packages considered during a resolve. Done means the metric reports the considered packages without changing default resolve behavior, with coverage for the reported result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100