9dcd98ad9c
In this commit, we attempt to fix a bug that's possible within the Start() method of the ChainArbiter. We pass the channel pointer directly into the newActiveChannelArbitrator function causing it to close over the loop variable. We later use the channel point directly to send messages to other sub-systems. It's possible that we actually have the shadowed loop variable and will send an incorrect message. Defensively, we now re-bind the loop variable in order to ensure we point to the proper channel. |
||
|---|---|---|
| .. | ||
| 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 | ||