• 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
server.go 32.3 KB