nodeDB.querySeeds was not safe for concurrent use but could be called
concurrenty on multiple goroutines in the following case:
- the table was empty
- a timed refresh started
- a lookup was started and initiated refresh
These conditions are unlikely to coincide during normal use, but are
much more likely to occur all at once when the user's machine just woke
from sleep. The root cause of the issue is that querySeeds reused the
same leveldb iterator until it was exhausted.
This commit moves the refresh scheduling logic into its own goroutine
(so only one refresh is ever active) and changes querySeeds to not use
a persistent iterator. The seed node selection is now more random and
ignores nodes that have not been contacted in the last 5 days.
update docker
update docker file
docker update 2
oi
docker again
update testnet block
update docker
update docker file
docker update 2
oi
docker again
update testnet block
update docker
update docker file
docker update 2
oi
docker again
docker2
docker3
fixed gvm
docker change
docking is meh
i hate docker
dockingsucks
update blockreward to 8
because its a lucky number 💃
update 60606 to 42786
60606 looks evil
42786 is my birthday
update jsre
replace eth for exp
update blocktime and test_genesis
fix test genesis
This commit changes the discovery protocol to use the new "v4" endpoint
format, which allows for separate UDP and TCP ports and makes it
possible to discover the UDP address after NAT.
