Daniel Knopik de6d597679 p2p/discover: schedule revalidation also when all nodes are excluded (#30239) ... ## Issue If `nextTime` has passed, but all nodes are excluded, `get` would return `nil` and `run` would therefore not invoke `schedule`. Then, we schedule a timer for the past, as neither `nextTime` value has been updated. This creates a busy loop, as the timer immediately returns. ## Fix With this PR, revalidation will be also rescheduled when all nodes are excluded. --------- Co-authored-by: lightclient <lightclient@protonmail.com>		2024-07-31 21:38:23 +02:00
..
v4wire
v5wire
common.go
lookup.go
metrics.go
node.go
ntp.go
table.go
table_reval.go	p2p/discover: schedule revalidation also when all nodes are excluded (#30239)	2024-07-31 21:38:23 +02:00
table_reval_test.go
table_test.go
table_util_test.go
v4_lookup_test.go
v4_udp.go
v4_udp_test.go
v5_talk.go
v5_udp.go
v5_udp_test.go