Olaoluwa Osuntokun 2099d6fa77

contractcourt: ensure we always cancel block epoch notifications after use ...

In this commit, we fix an existing grouting leak within the contract
court package. If a goroutine dies, but it doesn’t actually cancel the
block epoch notification that it requested, then it’s possible to leak
thousands of gorutines. To remedy this situation, we ensure that we’ll
*always* cancel the epoch notification once the goroutine has exited.

2018-02-05 14:41:08 -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: ensure we always cancel block epoch notifications after use

2018-02-05 14:41:08 -08:00

chain_watcher.go

contractcourt: properly use the broadcast state number during breach remedy

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: ensure we always cancel block epoch notifications after use

2018-02-05 14:41:08 -08:00

log.go

contractcourt: create new package, add logger

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