5476f6d310
This commit attempts to fix an inconsistency in when we consider an HTLC to expire. When we first launched the resolver we would compare the current block height against the expiry, while for new incoming blocks we would compare against expiry-1. This lead to a flake during integration tests, during a call to RestartNode after _exactly_ enough blocks for the HTLC to expire. In some cases the resolver would see the new blocks and consider the HTLC to be expired (because of the -1), while in some cases resolver would shut down before seeing the new blocks, and upon restart wouldn't act on the new height because we did not compare against -1. This commit fixes this by doing the same comparison in both cases. |
||
|---|---|---|
| .. | ||
| briefcase_test.go | ||
| briefcase.go | ||
| chain_arbitrator_test.go | ||
| chain_arbitrator.go | ||
| chain_watcher_test.go | ||
| chain_watcher.go | ||
| channel_arbitrator_test.go | ||
| channel_arbitrator.go | ||
| contract_resolvers_test.go | ||
| contract_resolvers.go | ||
| log.go | ||