Olaoluwa Osuntokun 5df6704a9c

contractcourt: make synchronous chain watcher notifications optional ...

In this commit, we modify the way that notifications are dispatched
within the chainWatcher. Before we would *always* wait for an ack back
before we started to clean up he database state. This would at times
lead to deadlocks. To remedy this, we now allow callers to decide if
they want notifications to be sync or not. The only current caller that
requires this is the breach arbiter.

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

..

briefcase_test.go

contractcourt: add new briefcase.go file to house persistent arbitrator state

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

briefcase.go

multi: fix linter warnings

2018-01-22 19:19:56 -08: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: make synchronous chain watcher notifications optional

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

chain_watcher.go

contractcourt: make synchronous chain watcher notifications optional

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

channel_arbitrator_test.go

contractcourt: add new ChannelArbitrator struct

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

channel_arbitrator.go

contractcourt: make synchronous chain watcher notifications optional

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

contract_resolvers_test.go

contractcourt: add complete ContractResolver implementations

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

contract_resolvers.go

contractcourt: add complete ContractResolver implementations

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

log.go

contractcourt: create new package, add logger

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