refactor: replace proof swap with state check in error recovery #1256
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!1256
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/better-automatic-reclaim"
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
This commit improves the proof recovery mechanism by replacing the swap operation with a more efficient state check approach when recovering from failed operations.
Fixes #1255
Notes to the reviewers
Suggested CHANGELOG Updates
CHANGED
ADDED
REMOVED
FIXED
Checklist
just final-checkbefore committing@ -30,9 +34,42 @@ impl<T: ?Sized> MaybeSend for T {}const BATCH_PROOF_SIZE: usize = 100;Why are we removing the transaction
@ -30,9 +34,42 @@ impl<T: ?Sized> MaybeSend for T {}const BATCH_PROOF_SIZE: usize = 100;This is a standard practice that I copied from other places, @thesimplekid. I'm fine with dropping this line. Wdyt?
@ -30,9 +34,42 @@ impl<T: ?Sized> MaybeSend for T {}const BATCH_PROOF_SIZE: usize = 100;Where else do we remove it? My intuition is that we shouldn't have to remove it and it should never be added if the tx fails. Since I don't believe we have a failed tx state and we only add successful ones.
These should be logs not prints.
LGTM. ACK
91e89a542d