theupdateframework / theupdateframework/specification
Spec should be explicit about what happens when no locally cached snapshot is available
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 405
- Forks
- 59
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 1
Description
For almost all files listed in the snapshot, if no locally cached snapshot is available this just means that they should be considered changed and should be downloaded. However, the root information is somewhat special in this respect: clients in initial state with root info but no snapshot yet should consider this situation to mean that the root information has not changed (otherwise this would loop indefinitely, because the downloaded snapshot should not be written to the local cache when we find we need to download new root info; see theupdateframework/specification#76).
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
Locate the specification section covering locally cached snapshots and root information. Clarify the behavior when no cached snapshot exists, especially for root information, and consider the issue complete when the distinction is explicit in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100