You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user calls abandon_payment, then restarts without freshly persisting the ChannelManager, the payment will still be pending on restart. This was unclear from the docs (and the docs seemed to imply otherwise). Because this doesn't materially impact the usability of abandon_payment (users shouldn't be called retry_payment on an abandoned one anyway), we simply document it.
Coverage data is based on head (9792ca3) compared to base (d9d4611).
Patch coverage: 50.00% of modified lines in pull request are covered.
❗ Current head 9792ca3 differs from pull request most recent head 1969b48. Consider uploading reports for the commit 1969b48 to get more accurate results
If a user calls `abandon_payment`, then restarts without freshly
persisting the `ChannelManager`, the payment will still be pending
on restart. This was unclear from the docs (and the docs seemed to
imply otherwise). Because this doesn't materially impact the
usability of `abandon_payment` (users shouldn't be called
`retry_payment` on an abandoned one anyway), we simply document it.
Fixeslightningdevkit#1804.
Squashed without further changes, diff from the other day is:
$ git diff-tree -U1 cf63c49 1969b48b7
diff --git a/lightning/src/ln/channelmanager.rs b/lightning/src/ln/channelmanager.rs
index 0aa89b5dc..29304cadb 100644
--- a/lightning/src/ln/channelmanager.rs+++ b/lightning/src/ln/channelmanager.rs@@ -2764,3 +2764,3 @@ impl<M: Deref, T: Deref, K: Deref, F: Deref, L: Deref> ChannelManager<M, T, K, F
/// After this method returns, no future calls to [`retry_payment`] for the given `payment_id`
- /// are allowed. If no such event has been generated, an [`Event::PaymentFailed`] event will be+ /// are allowed. If no [`Event::PaymentFailed`] event had been generated before, one will be
/// generated as soon as there are no remaining pending HTLCs for this payment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If a user calls
abandon_payment, then restarts without freshly persisting theChannelManager, the payment will still be pending on restart. This was unclear from the docs (and the docs seemed to imply otherwise). Because this doesn't materially impact the usability ofabandon_payment(users shouldn't be calledretry_paymenton an abandoned one anyway), we simply document it.Fixes#1804.