Fix listpays still pending when using xpay/injectpaymentonion#8635
Merged
rustyrussell merged 2 commits intoElementsProject:masterfrom Nov 4, 2025
Merged
Conversation
…t queue it to the channeld for the peer. Signed-off-by: Rusty Russell <[email protected]>
…sendpays "pending". If we failed after we register (e.g. channeld not available), we don't mark it failed. We shouldn't register until we've definitely created the htlc. Changelog-Fixed: `xpay` would sometimes leave payment parts status `pending` in failure cases (as seen in listpays or listsendpays). Signed-off-by: Rusty Russell <[email protected]> Fixes: ElementsProject#8629
rustyrussell
force-pushed
the
guilt/listpays-still-pending
branch
from
65db5d5 to
725b864
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes: #8629
There was a corner case where we created a pending payment but then didn't create an outgoing htlc (most simply, when the peer wasn't connected!). Test that, and fix the ordering, then finally add a db migration which cleans up any previous ones.