mirror of
https://github.com/Ride-The-Lightning/RTL.git
synced 2026-08-13 12:33:07 +02:00
89b6313a5b
sendPayment's timeout_seconds defaults to 600, equal to the wrapper's 600 s transport bound, so the transport timer (started first) would win the race and surface ECONNABORTED instead of LND's clean FAILURE_REASON_* result. The call now passes timeout_seconds plus a 60 s margin as the per-call transport timeout, so LND's mapped failure always arrives first while the transport stays bounded for the actual hang case (and a user-supplied timeout_seconds scales the bound with it). paymentLookup (/v2/router/track) deliberately keeps the 10-minute default: it holds a browser-facing response open while tracking, and payments in flight longer than that are delivered by the websocket subscription path instead. Documented at the call site. Verified on the fixture: a routed payment with an explicit timeout_seconds succeeds; an unroutable payment returns LND's mapped failure reason (Insufficient Balance - no ECONNABORTED, no transport timeout message); paymentLookup returns the final state of a settled payment. Both API suites re-pass. |
||
|---|---|---|
| .. | ||
| controllers | ||
| models | ||
| routes | ||
| utils | ||