30dbbd69a0
In this commit, we fix an existing bug that would result in some payments getting “stuck”. This would happen if one side restarted before the channel was fully locked in. In this case, since upon re-connection, the link will get added to the switch with a *short channel ID of zero*. If A then tries to make a multi-hop payment through B, B will fail to forward the payment, as it’ll mistakenly think that the payment originated from a local-subsystem as the channel ID is zero. A short channel ID of zero is used to map local payments back to their caller. With fix this by allowing the funding manager to dynamically update the short channel ID of a link after it discovers the short channel ID. In this commit, we fix a second instance of reported “stuck” payments by users. |
||
|---|---|---|
| .. | ||
| circuit_test.go | ||
| circuit.go | ||
| failure.go | ||
| interfaces.go | ||
| iterator.go | ||
| link_test.go | ||
| link.go | ||
| log.go | ||
| mailbox_test.go | ||
| mailbox.go | ||
| mock.go | ||
| packet.go | ||
| queue_test.go | ||
| queue.go | ||
| switch_test.go | ||
| switch.go | ||
| test_utils.go | ||