mirrors/arti.git - mirror of https://gitlab.torproject.org/tpo/core/arti

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	Use an mpsc::unbounded() channel in GuardMgr.	Nick Mathewson	2021-10-10	2	-29/+22
\| \| \| \| \| \| \| \| \| \| \| \|	The advantage here is that we no longer have to use a futures-aware Mutex, or a blocking send operation, and therefore can simplify a bunch of the GuardMgr APIs to no longer be async. That'll avoid having to propagate the asyncness up the stack. The disadvantage is that unbounded channels are just that: nothing in the channel prevents us from overfilling it. Fortunately, the process that consumes from the channel shouldn't block much, and the channel only gets filled when we're planning a circuit path.
*	enable checked_conversions lint.	Nick Mathewson	2021-10-09	1	-0/+1
\|
*	Normalize tor-guardmgr warnings	Nick Mathewson	2021-10-09	1	-6/+6
\|
*	Note a possible heisenbug in a unit test.	Nick Mathewson	2021-10-08	1	-0/+6
\|
*	Add a few tracing calls to tor-guardmgr.	Nick Mathewson	2021-10-08	3	-17/+74
\|
*	Update the tor-guardmgr README.md.	Nick Mathewson	2021-10-07	1	-1/+97
\|
*	Resolve small issues and XXXX/TODO comments in GuardMgr.	Nick Mathewson	2021-10-07	5	-48/+63
\| \| \| \| \|	By the time I merge this, most of the comments should have tickets to go with them.
*	Tests for top-level GuardMgr.	Nick Mathewson	2021-10-07	5	-23/+205
\| \| \| \| \| \| \|	Also, refactor our message handling to be more like the tor_proto reactors. The previous code had a bug where, once the stream of events was exhausted, we wouldn't actually get any more notifications.
*	Tests for tor_guardmgr::sample.	Nick Mathewson	2021-10-07	1	-1/+330
\|
*	Initial tests for tor_guardmgr::guard	Nick Mathewson	2021-10-07	2	-0/+296
\|
*	Implement persistent state for guard mgr	Nick Mathewson	2021-10-07	2	-10/+26
\|
*	Initial backend implementation for guard node manager.	Nick Mathewson	2021-10-07	9	-0/+2502
	There are some missing parts here (like persistence and tests) and some incorrect parts (I am 90% sure that the "exploratory circuit" flag is bogus). Also it is not integrated with the circuit manager code.