AcademySoftwareFoundation / AcademySoftwareFoundation/rez
avoid non-cachable packages in cache
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 374
- Avg merge
- 9d 12h
- Merged PRs (30d)
- 5
Description
The following scenario is possible:
* pkg A is cached
* the rezconf is updated to set pkg A to NON-cachable
* a new resolve picks up cached A
We could add a step that checks if the pkg is still cachable, after it finds a cached copy. If it isn't, the cached copy is not used.
Related - if `rez-pkg-cache --clean` is run, and it finds a cache entry for a pkg that is no longer cachable, it should delete that cache entry.
Contributor guide
Research direction
Trace the resolver path that uses a cached package, then inspect the `rez-pkg-cache --clean` handling of cache entries. Verify both paths check whether the package remains cachable, and confirm that non-cachable packages are neither reused nor retained by cleanup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100