Bug: Handle Send Errors for CLN
Closed this issue · 0 comments
carlaKC commented
When CLN fails a payment (eg, because there's no route), they'll fail the entire API call rather than sending back an okay response containing an error code. This will shut down the simulation, so we'll need to add some error handling.
My instinct would be to take a look at the error code they're giving us (hopefully that helps classify pathfinding errors vs terminal errors).
ERROR [sim_lib] Error while sending payment 0366dc9e42d6cb2a89d3ba9a347a0995c88e62949618db6f62bd86fd1da0364868
-> 02c0c6b8be1a367c2fce4efdd9ea075b1e2b15d2566c6eab845513a88e313ee0ab.
Terminating consumer. Send payment error status:
Unknown, message: "Error calling method KeySend: RpcError {
code: Some(210), message: \"Ran out of routes to try after 1 attempt: see `paystatus`\" }", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Mon, 11 Sep 2023 15:48:33 GMT", "content-length": "0"}
}