eeeb0f6f0e
Blockchain's notificationDispatcher sends events to channels and these channels must be read from. Unfortunately, regular service shutdown procedure does unsubscription first (outside of the read loop) and only then drains the channel. While it waits for unsubscription request to be accepted notificationDispatcher can try pushing more data into the same channel which will lead to a deadlock. Reading in the same method solves this, any number of events can be pushed until unsub channel accepts the data. |
||
|---|---|---|
| .. | ||
| testdata | ||
| core_test.go | ||
| node.go | ||
| node_test.go | ||
| notary.go | ||
| notary_test.go | ||
| request_type.go | ||