8 Commits (86fe359a5678ec5958e9eb4caefe4b3ff36bcc2d)

Author	SHA1	Message	Date
Felix Lange	f26c19cbcd	common/mclock: remove dependency on github.com/aristanetworks/goarista (#22211) ... It takes three lines of code to get to runtime.nanotime, no need to pull a dependency for that.	4 years ago
Boqin Qin	1b9c5b393b	all: fix goroutine leaks in unit tests by adding 1-elem channel buffer (#20666) ... This fixes a bunch of cases where a timeout in the test would leak a goroutine.	5 years ago
Felix Lange	c22fdec3c7	common/mclock: add NewTimer and Timer.Reset (#20634) ... These methods can be helpful when migrating existing timer code.	5 years ago
Felix Lange	b1c3010bf2	common/mclock: clean up AfterFunc support (#20054) ... This change adds tests for the virtual clock and aligns the interface with the time package by renaming Cancel to Stop. It also removes the binary search from Stop because it complicates the code unnecessarily.	5 years ago
Felföldi Zsolt	a7de796840	les: implement new client pool (#19745)	5 years ago
Felföldi Zsolt	b2ddb1fcbf	les: implement client connection logic (#16899) ... This PR implements les.freeClientPool. It also adds a simulated clock in common/mclock, which enables time-sensitive tests to run quickly and still produce accurate results, and package common/prque which is a generalised variant of prque that enables removing elements other than the top one from the queue. les.freeClientPool implements a client database that limits the connection time of each client and manages accepting/rejecting incoming connections and even kicking out some connected clients. The pool calculates recent usage time for each known client (a value that increases linearly when the client is connected and decreases exponentially when not connected). Clients with lower recent usage are preferred, unknown nodes have the highest priority. Already connected nodes receive a small bias in their favor in order to avoid accepting and instantly kicking out clients. Note: the pool can use any string for client identification. Using signature keys for that purpose would not make sense when being known has a negative value for the client. Currently the LES protocol manager uses IP addresses (without port address) to identify clients.	6 years ago
kiel barry	d0fd8d6fc2	common: all golint warnings removed (#16852) ... * common: all golint warnings removed * common: fixups	6 years ago
Zsolt Felfoldi	9f8d192991	les: light client protocol and API	8 years ago