-
Notifications
You must be signed in to change notification settings - Fork 213
Commit
2160: Test that `removePools` does not remove pool metadata. r=KtorZ a=jonathanknowles # Issue Number #2154 # Overview This PR adds documentation and tests that `removePools` does not remove metadata. Strictly speaking, when removing pools, we should also be able to remove any pool metadata that becomes unreachable as a result. However, this is tricky to get right, since it's possible for more than one pool to share the same metadata hash. For example, if two pools **_p_** and **_q_** issue registration certificates that share the same metadata hash **_h_**, and then we garbage collect pool **_p_**, we have to be careful to not remove the metadata corresponding to h in order to preserve the metadata for pool **_q_**. One possible solution would be to remove metadata entries only when we can show that they are no longer reachable: when metadata entries are no longer referenced by any pool. However, for the moment, we adopt the principle of never removing metadata. We can revise this decision in future if the metadata table grows too large. 2165: Bump version to v2020-09-22 r=Anviking a=Anviking # Issue Number Release # Overview - [x] Bump version using `./scripts/make_release.sh` # Comments <!-- Additional comments or screenshots to attach if any --> <!-- Don't forget to: ✓ Self-review your changes to make sure nothing unexpected slipped through ✓ Assign yourself to the PR ✓ Assign one or several reviewer(s) ✓ Once created, link this PR to its corresponding ticket ✓ Assign the PR to a corresponding milestone ✓ Acknowledge any changes required to the Wiki --> Co-authored-by: Jonathan Knowles <jonathan.knowles@iohk.io> Co-authored-by: Johannes Lund <johannes.lund@iohk.io> Co-authored-by: Rodney Lorrimar <rodney.lorrimar@iohk.io>
- Loading branch information
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.