-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pool DB operation removeRetiredPools
.
#2047
Conversation
8d5c7cb
to
b7636eb
Compare
76d56dc
to
e048243
Compare
In response to review feedback here: #2047 (comment)
In response to review feedback here: #2047 (comment)
c912a26
to
e7810ad
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
b7636eb
to
6039042
Compare
In response to review feedback here: #2047 (comment)
e7810ad
to
5b6f5af
Compare
0741d66
to
b5f1579
Compare
cb87439
to
70a3cfd
Compare
In response to review feedback here: #2047 (comment)
5b6f5af
to
83baaae
Compare
In response to review feedback here: #2047 (comment)
83baaae
to
ed4a446
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two comments about logging for you to address. Since removeRetiredPools
is not used anywhere I assume there will be another PR.
That's correct. From the PR description:
|
Grammatically, the generated text now makes sense regardless of whether the retirement is in the future or the past.
Rename `retiredIn` to `retirementEpoch` in `PoolRetirementCertificate`. The phrase "retired in" is somewhat ambiguous, as it might lead readers to believe that a pool has already retired, when in fact this value can refer to an epoch that is still in the future. In comparison, the phrase "retirement epoch" is neutral w.r.t. whether the epoch is in the future or the past.
In preparation for bracket-style logging.
In response to review feedback here: #2047 (comment)
To avoid cyclic module dependencies.
In response to review feedback: #2047 (comment)
For: - MsgRemovingRetiredPools - MsgRemovingRetiredPoolsForEpoch In response to review feedback: #2047 (comment)
5f9c7df
to
024d36b
Compare
bors r+ |
Build succeeded |
Issue Number
#2018
Overview
Building on the work added in PRs #2024 and #2038, this PR:
removeRetiredPools
operation to the pool DB layer:MsgRemovingRetiredPools
message to the log whenever theremoveRetiredPools
operation is called:Further Work
Before garbage collection can actually happen, the wallet needs to call
removeRetiredPools
at appropriate intervals. This work is deferred to a future PR.See issue #2019.