Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make length and hashes optional in snapshot/timestamp metadata
See original GitHub issueDescription of issue or feature request:
As per the specification (v1.0.1) length and hashes fields in timestamp and snapshot metadata are optional. The reference implementation should reflect this.
Current behavior:
- timestamp metadata always includes length and hashes of snapshot metadata (see
reposoitory_lib.generate_timestamp_metadata) - snapshot metadata always excludes length and hashes of (delegated) targets metadata (see
repository_lib.generate_snapshot_metadata)
Expected behavior:
Add option to include/exclude these fields in the relevant functions in repository_lib. Since these functions are usually called via write/writeall the option should be made available there too. It’s also conceivable to configure this via attributes on the Repository object.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@joshuagl can you close this one? It’s fixed by the above pr.
I suggest to choose them so that the default behavior of these functions matches their current behavior.