• Felix Lange's avatar
    p2p: ensure Server.loop is ticking even if discovery hangs (#20573) · d5acc5ed
    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 Loading commit data...
dnsdisc Loading commit data...
enode Loading commit data...
enr Loading commit data...
nat Loading commit data...
netutil Loading commit data...
simulations Loading commit data...
testing Loading commit data...
dial.go Loading commit data...
dial_test.go Loading commit data...
message.go Loading commit data...
message_test.go Loading commit data...
metrics.go Loading commit data...
peer.go Loading commit data...
peer_error.go Loading commit data...
peer_test.go Loading commit data...
protocol.go Loading commit data...
rlpx.go Loading commit data...
rlpx_test.go Loading commit data...
server.go Loading commit data...
server_test.go Loading commit data...
util.go Loading commit data...
util_test.go Loading commit data...