Skip to content
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

Expose a failure reason in PaymentFailed #2142

Conversation

alecchendev
Copy link
Contributor

Closes #2095. Adds a new public enum PaymentFailureReason and a new field on Event::PaymentFailed to communicate why the payment failed completely.

Copy link
Contributor Author

@alecchendev alecchendev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some things I’m considering changing right now if anyone wants to give some feedback:

lightning/src/events/mod.rs Outdated Show resolved Hide resolved
lightning/src/ln/outbound_payment.rs Outdated Show resolved Hide resolved
@codecov-commenter
Copy link

codecov-commenter commented Apr 1, 2023

Codecov Report

Patch coverage: 80.00% and project coverage change: +0.24 🎉

Comparison is base (f30dc85) 91.38% compared to head (23c7064) 91.62%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2142      +/-   ##
==========================================
+ Coverage   91.38%   91.62%   +0.24%     
==========================================
  Files         102      102              
  Lines       50288    52337    +2049     
  Branches    50288    52337    +2049     
==========================================
+ Hits        45954    47954    +2000     
- Misses       4334     4383      +49     
Impacted Files Coverage Δ
lightning/src/ln/channelmanager.rs 92.38% <ø> (+3.02%) ⬆️
lightning/src/events/mod.rs 33.76% <37.50%> (+0.07%) ⬆️
lightning/src/ln/outbound_payment.rs 90.01% <77.77%> (-0.68%) ⬇️
lightning/src/ln/functional_test_utils.rs 92.47% <100.00%> (+0.01%) ⬆️
lightning/src/ln/functional_tests.rs 98.25% <100.00%> (ø)
lightning/src/ln/onion_route_tests.rs 98.48% <100.00%> (+<0.01%) ⬆️
lightning/src/ln/payment_tests.rs 97.45% <100.00%> (+<0.01%) ⬆️

... and 9 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Copy link
Collaborator

@TheBlueMatt TheBlueMatt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great, thanks!

lightning/src/events/mod.rs Outdated Show resolved Hide resolved
lightning/src/events/mod.rs Outdated Show resolved Hide resolved
lightning/src/events/mod.rs Outdated Show resolved Hide resolved
lightning/src/ln/outbound_payment.rs Outdated Show resolved Hide resolved
@TheBlueMatt TheBlueMatt added this to the 0.0.115 milestone Apr 3, 2023
@alecchendev alecchendev force-pushed the 2023-03-expose-fail-reason-in-payment-failure branch 3 times, most recently from 387d455 to 0383f8b Compare April 4, 2023 03:41
@alecchendev
Copy link
Contributor Author

Squashed to pass CI and because it was getting messy to read all the fixups since I was changing/merging enum variants and had to undo work from previous commits.

@alecchendev alecchendev marked this pull request as ready for review April 4, 2023 03:48
lightning/src/events/mod.rs Outdated Show resolved Hide resolved
lightning/src/events/mod.rs Outdated Show resolved Hide resolved
lightning/src/ln/outbound_payment.rs Outdated Show resolved Hide resolved
lightning/src/events/mod.rs Outdated Show resolved Hide resolved
@alecchendev
Copy link
Contributor Author

alecchendev commented Apr 4, 2023

Separating my fixup commits so they're easier to squash later even though it'll fail CI how they currently are.

lightning/src/events/mod.rs Outdated Show resolved Hide resolved
lightning/src/ln/outbound_payment.rs Outdated Show resolved Hide resolved
lightning/src/ln/outbound_payment.rs Show resolved Hide resolved
lightning/src/ln/outbound_payment.rs Outdated Show resolved Hide resolved
lightning/src/ln/outbound_payment.rs Outdated Show resolved Hide resolved
@alecchendev alecchendev force-pushed the 2023-03-expose-fail-reason-in-payment-failure branch from 4e7731d to 3b11ebb Compare April 5, 2023 19:58
@alecchendev alecchendev force-pushed the 2023-03-expose-fail-reason-in-payment-failure branch from 3b11ebb to caf991b Compare April 5, 2023 21:21
Copy link
Contributor

@valentinewallace valentinewallace left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good!

lightning/src/events/mod.rs Outdated Show resolved Hide resolved
lightning/src/events/mod.rs Outdated Show resolved Hide resolved
lightning/src/ln/outbound_payment.rs Outdated Show resolved Hide resolved
@valentinewallace
Copy link
Contributor

Feel free to squash!

@alecchendev alecchendev force-pushed the 2023-03-expose-fail-reason-in-payment-failure branch from caf991b to 7cf9094 Compare April 7, 2023 01:09
Copy link
Contributor

@valentinewallace valentinewallace left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after squash

@alecchendev alecchendev force-pushed the 2023-03-expose-fail-reason-in-payment-failure branch 3 times, most recently from 207a3d4 to 17e8d4b Compare April 7, 2023 18:26
@alecchendev
Copy link
Contributor Author

Rebased and fixed 2 lines for CI - payment_tests.rs line 2924 (the change here doesn't really relate to this PR, don't really know what's normal to do here) and 2959

@TheBlueMatt
Copy link
Collaborator

Oops that was just fixed in #2170.

@alecchendev alecchendev force-pushed the 2023-03-expose-fail-reason-in-payment-failure branch from 17e8d4b to 4ba183d Compare April 7, 2023 18:46
@alecchendev
Copy link
Contributor Author

Rebased again so it's not showing the overlapping change :)

Comment on lines 835 to 829
log_error!(logger, "Failed to send along path due to error: {:?}", e);
if let APIError::MonitorUpdateInProgress = e { continue }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a big deal, but ideally we shouldn't log_error if we get APIError::MonitorUpdateInProgress, because it's not an error (🙄). Could conditionally log or move the current log to after the continue

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah thanks

@@ -1232,7 +1226,7 @@ impl OutboundPayments {
} else {
PaymentFailureReason::RetriesExhausted
};
let _ = payment.get_mut().mark_abandoned(reason); // we'll only Err if it's a legacy payment
payment.get_mut().mark_abandoned(reason); // we'll only Err if it's a legacy payment
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can remove the comment

@alecchendev alecchendev force-pushed the 2023-03-expose-fail-reason-in-payment-failure branch from 508d860 to 5251b39 Compare April 10, 2023 20:15
Copy link
Contributor

@valentinewallace valentinewallace left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after squash

This includes adding a reason to `PendingOutboundPayment::Abandoned` and
using that reason when pushing an `Event::PaymentFailed`.
@alecchendev alecchendev force-pushed the 2023-03-expose-fail-reason-in-payment-failure branch from 5251b39 to 23c7064 Compare April 10, 2023 22:14
@valentinewallace valentinewallace merged commit 157af6e into lightningdevkit:main Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Expose a failure reason in PaymentFailure
4 participants