-
-
Couldn't load subscription status.
- Fork 371
fix: pay invoice status #2481
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
fix: pay invoice status #2481
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #2481 +/- ##
==========================================
+ Coverage 61.81% 61.83% +0.01%
==========================================
Files 67 67
Lines 9583 9611 +28
==========================================
+ Hits 5924 5943 +19
- Misses 3659 3668 +9 ☔ View full report in Codecov by Sentry. |
767cecc to
117c93a
Compare
50c949a to
5def2b8
Compare
d09731c to
37defa4
Compare
|
Note: regtest fails for reasons outside this PR. Should be fixed soon. |
6fb7293 to
40f938d
Compare
40f938d to
68dfef7
Compare
Summary
This PR addresses an issue for failed
outgoing payments.If an outgoing payment (invoice paid by the user) is marked as failed, then it will be deleted after a certain time interval.
The (current) reason for deleting the failed outgoing payment is to unlock the user funds. Because while the payment is still present the amount is considered locked.
The issue is that sometimes the
outgoing paymentcan be marked as failed for technical reason, BUT the invoice is not actually canceled.The solution in this PR is to:
failedunless the funding source explicitly returns a status that says the payment is failedpendingget_payment_statusfor all funding sources returnsfailedunder some conditionalbyandpoenixdhave an issue here