forked from TrueCloudLab/neoneo-go
af6a6f5f30
There is a notification pushed into the channel when block is being added, that notification is read by special goroutine that then forwards it to all subscribers to that particular event. Consensus goroutine is one of that subscribers, so for the system to properly function it has to read these events, but at the same time it can generate new blocks inside, so in some cases it can generate two blocks without ever reading from the subscription channel and this will lead to a deadlock. To avoid that we need to check subscription channel for events on every loop. |
||
|---|---|---|
| .. | ||
| compiler | ||
| config | ||
| consensus | ||
| core | ||
| crypto | ||
| encoding | ||
| internal | ||
| interop | ||
| io | ||
| network | ||
| rpc | ||
| smartcontract | ||
| util | ||
| vm | ||
| wallet | ||