Dmitry Shulyak fa526e7444 Prevent potential call on discv5 which became nil ... It could happen when we found multiple relevant peers and they were processed before discv5 closed. For example we have max limit of 1: - found peer A and B in the same kademlia cycle - process peer A - max limit is reached -> closed discv5 and set it to nil - process peer B - panic!!!		2018-04-19 16:01:48 +03:00
..
cache.go	Peer pool to manage v5 peers (#736)	2018-04-10 09:44:09 +03:00
cache_test.go	Peer pool to manage v5 peers (#736)	2018-04-10 09:44:09 +03:00
discv5.go	Peerpool failover (#801)	2018-04-12 16:08:49 +03:00
peerpool.go	Prevent potential call on discv5 which became nil	2018-04-19 16:01:48 +03:00
peerpool_test.go	Prevent potential call on discv5 which became nil	2018-04-19 16:01:48 +03:00
topic_register.go	Peer pool to manage v5 peers (#736)	2018-04-10 09:44:09 +03:00
topicpool.go	Fix two race conditions in peerpool tests (#827)	2018-04-13 11:34:30 +03:00
topicpool_test.go	Peerpool failover (#801)	2018-04-12 16:08:49 +03:00