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.

Sign up for GitHub

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

Jump to bottom

Bug: ExpiryTooFar should be detected #75

Open
C-Otto opened this issue Nov 16, 2022 · 1 comment
Open

Bug: ExpiryTooFar should be detected #75

C-Otto opened this issue Nov 16, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@C-Otto
Copy link
Owner

C-Otto commented Nov 16, 2022

Describe the bug
When sending out a payment with a "total time lock" exceeding the configured value for max-cltv-expiry, the SendToRoute invocation fails. This error is not detected/logged.

To Reproduce
Send a payment through nodes with high CLTV delta values.

Expected behavior
The error is logged/shown to the user.
@C-Otto C-Otto added the bug Something isn't working label Nov 16, 2022
This was referenced Nov 16, 2022
Closed
Closed
@C-Otto
Copy link
Owner Author

C-Otto commented Nov 16, 2022 •
edited
Loading

This is related to #38. The information shown to the user is provided via PaymentStatus, whereas the actual payment loop uses PaymentInformation in MultiPathPaymentObserver. Non-final errors, including the common "temporary channel failure", are not provided to PaymentStatus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@C-Otto