tendermint

Commit Graph

Author	SHA1	Message	Date
Sean Braithwaite	fbede85e20	changes based on feedback	5 years ago
Sean Braithwaite	e7ee314c99	Subsume the demuxer into the reactor + Simplify the design by demuxing events directly in the reactor	5 years ago
Sean Braithwaite	c62b7fbd7e	feedback tweaks	5 years ago
Sean Braithwaite	5474528db1	Switch to a priority queue: * Routines will now use a priority queue instead of channels to iterate over events	5 years ago
Sean Braithwaite	9d41770a99	Close rdy channel + close `rdy` channel to ensure that calls to `<-ready()` will always return if the routine is ready	5 years ago
Sean Braithwaite	f81c319ece	Add some docs	5 years ago
Sean Braithwaite	78d4c3b88a	fixes based on feedback	5 years ago
Sean Braithwaite	2c8cbfc26a	linter fixes	5 years ago
Sean Braithwaite	acbfe67fb8	set logger	5 years ago
Sean Braithwaite	aeac4743cc	typo fix	5 years ago
Sean Braithwaite	e826ca3c49	demuxer cleanup	5 years ago
Sean Braithwaite	5b880fbcff	cleanup events	5 years ago
Sean Braithwaite	c081b60ef6	Solidify API: + use `trySend` the replicate peer sending + expose `next()` as a chan of events as output + expose `final()` as a chan of error, for the final error + add `ready()` as chan struct when routine is ready	5 years ago
Sean Braithwaite	e4913f533a	Fix race condition in shutdown: + ensure that we stop accepting messages once `stop` has been called to avoid the case in which we attempt to write to a channel which has already been closed	5 years ago
Sean Braithwaite	0cf9f86292	Modification based on feedback + `routine.send` returns false when routine is not running + this will prevent panics sending to channels which have been closed + Make output channels routine specific removing the risk of someone writting to a channel which was closed by another touine. + consistency changes between the routines and the demuxer	5 years ago
Sean Braithwaite	0cf8812b17	[blockchain] v2 riri Schedule composit data structure (#3848 ) * Add Schedule: + The schedule is a data structure used to determine the optimal schedule of requests to the optimal set of peers in order to perform fast-sync as fast and efficiently as possible. * Add some doc strings * fix golangci * Add Schedule: + The schedule is a data structure used to determine the optimal schedule of requests to the optimal set of peers in order to perform fast-sync as fast and efficiently as possible. * Add some doc strings * remove globals from tests	5 years ago
Sean Braithwaite	d1671d6175	blockchain v2: routines + Include an implementaiton of the routines specified in ADR-43 along with a demuxer and some dummy reactor code	5 years ago

1 2

70 Commits (a3205267a93254c6a8cca52a27ba5721ff2adb68)