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

[bug]: payment_failure_reason > 0 when payment status = SUCCEEDED #8884

Open
rsafier opened this issue Jul 1, 2024 · 0 comments
Open

[bug]: payment_failure_reason > 0 when payment status = SUCCEEDED #8884

rsafier opened this issue Jul 1, 2024 · 0 comments
Labels
bug Unintended code behaviour needs triage

Comments

@rsafier
Copy link

rsafier commented Jul 1, 2024

Background

Appears since 0.18.0 some payments now occasional will have payment_failure_reason not equal to FAILURE_REASON_NONE despite payment being in SUCCEEDED status, and having preimage recorded.

Your environment

  • lnd 0.18.0-beta
  • Linux ip-100-0-1-117 6.5.0-1020-aws 22.04.1-Ubuntu SMP Wed May 1 16:10:50 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  • bitcoind backend

Steps to reproduce (only works on 0.18.0 and daily-testing-only dockerimage, 0.17.5 does not show this behavior)

  • Make network Alice->Bob->Carol
  • Have HTLC interceptor delay all traffic by 30s on Bob
  • Have Carol pay invoice on Alice with TimeoutSeconds set at 15s on the SendPaymentV2 request.
  • Original blocking payment will return SUCCEEDED and FAILURE_REASON_NONE
  • TrackPayment again and will return SUCCEEDED and FAILURE_REASON_TIMEOUT

C# unit test of behavior

Expected behaviour

if payment status equals SUCCEEDED then payment_failure_reason should be reported back as FAILURE_REASON_NONE as in prior LND versions.

Actual behaviour

Some payments in SUCCEEDED status also have non-zero payment_failure_reason set

@rsafier rsafier added bug Unintended code behaviour needs triage labels Jul 1, 2024
@rsafier rsafier changed the title [bug]: payment_failure_reason > 0 when payment status = SUCCESSFUL [bug]: payment_failure_reason > 0 when payment status = SUCCEEDED Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unintended code behaviour needs triage
Projects
None yet
Development

No branches or pull requests

1 participant