fix: pass final_expiry through in DbSignatory::rotate_keyset #1686
No reviewers
Labels
No labels
DB & Storage
Deployment
Error Handling & Logging
Maintenance
Payment Backend
backport
backport v0.13.x
backport v0.14.x
backport v0.15.x
bindings
blocked
bug
cdk-sql
ci
cli
deps
documentation
duplicate
enhancement
good first issue
help wanted
invalid
keep-open
ldk-node-ui
migrations
mint
mutation-testing
needs rebase
needs review
new nut
nut change
question
ready
rust-version
rustfmt
stacked hold
stale
testing
wallet
weekly-report
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
cashubtc/cdk!1686
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/final-expiry-passthrough"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
The
final_expiryfield fromRotateKeyArgumentswas hardcoded toNoneinDbSignatory::rotate_keyset, causing any expiry set during keyset rotation to be silently discarded. Now correctly forwardsargs.final_expirytocreate_new_keyset.Notes to the reviewers
Single-line fix. The
create_new_keysetfunction already acceptsfinal_expiry: Option<u64>andRotateKeyArgumentsalready carries the field it just wasn't being passed through.Suggested CHANGELOG Updates
CHANGELOG Updates
CHANGED
ADDED
REMOVED
FIXED
final_expirypassthrough inDbSignatory::rotate_keysetwas hardcoded toNone, now correctly uses the value fromRotateKeyArgumentsChecklist
just final-checkbefore committingLooks like we also need to set it here. Ideally we could add a test were we call rotate on the mint with an expiry and check it is set correctly. We do not need to use the grpc for this test, just rotate with an expiry directly on the mint.
github.com/cashubtc/cdk@e3f8dd0bab/crates/cdk/src/mint/keysets/mod.rs (L92)Thanks for adding the tests.
LGTM