mirrors/arti.git/crates/tor-circmgr/src/timeouts/pareto.rs, branch arti-v0.0.2

add semicolons if nothing returned

2021-11-25T13:20:37Z

Add #[serde(flatten)] HashMap fields to serializable objects

2021-10-27T12:31:52Z

As per arti#175, we'd like to be able to handle newer Arti versions storing additional state in the persisted state files, without dropping this data on the floor when we write out changes to these files. Use the #[serde(flatten)] mechanism to achieve this, by adding catch-all HashMap fields to all structs that are at risk of this happening to them.

Add a timeout estimator to take estimates from another process.

2021-10-20T16:41:59Z

Allow type of timeout estimator to change at runtime.

2021-10-20T16:06:58Z

This is a big change, but it does simplify the type of Builder a little, and isolates locking across different (potential) timeout estimator types.

enable checked_conversions lint.

2021-10-09T20:53:13Z

Initial backend implementation for guard node manager.

2021-10-07T14:45:42Z

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.

fix/silence clippy lints in test modules

2021-09-08T15:28:31Z

More tests in pareto.rs

2021-09-08T13:18:23Z

Use same defaults for abandon and close times in timeout code.

2021-09-07T18:53:50Z

On torspec!40, Mike says: I don't think there is a practical difference here. As per Section 2.4.5, if 60 seconds is not enough and causes the liveness test to fail due to too many timeouts, we will double the initial timeout. This makes our behavior the same as C tor.

Stop making abandoned/successful circuit counts persistent

2021-09-07T18:50:36Z

The C Tor implementation doesn't do this, and Mike says: I think it is a reasonable enough assumption that if Tor has restarted, this kind data is no longer fresh enough to be accurate for this purpose. This is also only 20 circuits here, and typical timeouts are now around 1-2 seconds or less.. So a restarted client with a timeout that is too low for a new internet connection will figure this out pretty quickly. I think that is OK. (from torspec!40)