Olaoluwa Osuntokun 9dcd98ad9c contractcourt: prevent scoping bug by re-binding channel pointer ...

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.

2018-05-18 16:21:06 -07:00

..

briefcase_test.go

build+multi: switch from bolt to bbolt

2018-03-10 19:01:13 -08:00

briefcase.go

contractcourt: define StateCommitmentBroadcasted

2018-04-25 09:37:22 +02:00

chain_arbitrator_test.go

contractcourt: add new ChainArbitrator struct as central coordinator of package

2018-01-22 19:19:36 -08:00

chain_arbitrator.go

contractcourt: prevent scoping bug by re-binding channel pointer

2018-05-18 16:21:06 -07:00

chain_watcher_test.go

contractcourt: update chain watcher tests to latest API

2018-05-03 21:29:30 -07:00

chain_watcher.go

multi: use mutex-guarded ShortChanID() on OpenChannel

2018-05-09 16:06:49 -07:00

channel_arbitrator_test.go

contractcourt test: add TestChannelArbitratorLocalForceDoubleSpend

2018-05-14 14:21:06 +02:00

channel_arbitrator.go

contractcourt/channel_arbitrator: remove unused transationTrigger

2018-04-25 09:37:25 +02:00

contract_resolvers_test.go

contractcourt: add complete ContractResolver implementations

2018-01-22 19:19:36 -08:00

contract_resolvers.go

multi: fix typos in comments

2018-04-17 19:03:27 -07:00

log.go

contractcourt: create new package, add logger

2018-01-22 19:19:34 -08:00