Open mauricepoirrier opened 1 month ago
Yes @mauricepoirrier I completely agree with this! It's been on my list of things to do. 😅 I think making the timeout configurable would be very nice. We could probably lower the default timeout to like 30 seconds as well.
If you're interested in working on this, go for it! (And if you do, please feel free to let me know if you have any questions about the LNDK code etc.)
Thank you @orbitalturtle, I'll work on this!
Double check on the solution, making the timeout configurable means changing from the config file or the paramenters on the request, both or either 😅?
Good point, I like the idea of adding a parameter to the request, in case the user wants to try different timeouts without having to restart LNDK.
Feature Description
I've been playing with bolt12-playground and every now and then I mess up the network and I can't pay from lndk to another node (e.g., lndk-> eclair or lndk -> lndk). The node fails to find a path for sending the payment, and the cmd hangs for ~2 minutes. Logs indicate a failure to find a path and a timeout when waiting for an invoice.
Problems identified
Design
Double checking the code, when node sends the invoice request message through if something happen while connecting to peer it doesn't handle any error (or timeout if building the route in the future)
Proposed solutions