theupdateframework / theupdateframework/rust-tuf
Should we stop directly storing metadata MetadataVersion::None?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 198
- Forks
- 39
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
As part #151, I started making rust-tuf concurrent. This means however that some previously safe patterns, like storing metadata both as MetadataVersion::Number(X) and MetadataVersion::None to signify it as the latest version is now racy since other threads can compete on updating metadata. What do you think about getting rid of MetadataVersion::None, and changing Repository::fetch_metadata to take a Option<MetadataVersion>, where None signifies getting the newest version?
Contributor guide
No contributing guide indexed for this repository
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 reviewing MetadataVersion and the Repository::fetch_metadata entry point, along with their usages, to understand how MetadataVersion::None currently represents the latest version. A complete outcome requires a settled API decision for the concurrent case and agreement on the resulting metadata-fetching behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100