-
Notifications
You must be signed in to change notification settings - Fork 345
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
Expose a failure reason in PaymentFailed
#2142
Conversation
There was a problem hiding this 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:
Codecov ReportPatch coverage:
📣 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
... 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. |
There was a problem hiding this 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!
387d455
to
0383f8b
Compare
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. |
Separating my fixup commits so they're easier to squash later even though it'll fail CI how they currently are. |
fa682d4
to
a58bfa6
Compare
4e7731d
to
3b11ebb
Compare
3b11ebb
to
caf991b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good!
Feel free to squash! |
caf991b
to
7cf9094
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after squash
207a3d4
to
17e8d4b
Compare
Rebased and fixed 2 lines for CI - |
Oops that was just fixed in #2170. |
17e8d4b
to
4ba183d
Compare
Rebased again so it's not showing the overlapping change :) |
lightning/src/ln/outbound_payment.rs
Outdated
log_error!(logger, "Failed to send along path due to error: {:?}", e); | ||
if let APIError::MonitorUpdateInProgress = e { continue } |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah thanks
lightning/src/ln/outbound_payment.rs
Outdated
@@ -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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can remove the comment
508d860
to
5251b39
Compare
There was a problem hiding this 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`.
5251b39
to
23c7064
Compare
Closes #2095. Adds a new public enum
PaymentFailureReason
and a new field onEvent::PaymentFailed
to communicate why the payment failed completely.