-
Felix Lange authored
This is a temporary fix for a problem which started happening when the dialer was changed to read nodes from an enode.Iterator. Before the iterator change, discovery queries would always return within a couple seconds even if there was no Internet access. Since the iterator won't return unless a node is actually found, discoverTask can take much longer. This means that the 'emergency connect' logic might not execute in time, leading to a stuck node.
d5acc5ed
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
discover | Loading commit data... | |
discv5 | ||
dnsdisc | ||
enode | ||
enr | ||
nat | ||
netutil | ||
simulations | ||
testing | ||
dial.go | ||
dial_test.go | ||
message.go | ||
message_test.go | ||
metrics.go | ||
peer.go | ||
peer_error.go | ||
peer_test.go | ||
protocol.go | ||
rlpx.go | ||
rlpx_test.go | ||
server.go | ||
server_test.go | ||
util.go | ||
util_test.go |