Potential use case: setting "repository_version" on the distribution freezes the registry
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 4
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 6
Description
Setting repository_version on a Distribution would currently be a useless configuration, because requests for content not in the repo would still fall back to the proxy and modify the repository behind your back - functionally identical if not strictly worse than just setting repository in the first place.
What we could do instead is disable the fallback entirely if repository_version was set, turning the registry "frozen"
This would be simple to do with a tweak to get_rvc().
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 locating get_rvc() and trace how repository_version requests currently reach the proxy fallback. The change is complete when setting repository_version prevents fallback requests and keeps the registry from being modified by missing content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100