mirrors/arti.git/crates/tor-guardmgr/src/fallback.rs, branch arti-v0.5.0

impl_standard_builder: Use for tor_guardmgr::FallbackDir

2022-06-16T14:42:06Z

config derive attrs: Make builders serde, and validated structs not

2022-05-05T09:35:52Z

* Builders additionally derive: Debug, Serialize, Deserialize. * Validated structs no longer derive: Serialize, Deserialize and all related attributes deleted. * As a consequence, all the `#[serde(deny_unknown_fields)]` are gone. That means that right now unknown fields are totally ignored. This is good for compatibility but poor for useability. Doing something better here is arti#417, in progress. * As a consequence, delete tor_dirmgr::retry::default_parallelism. (The default value was already duplicated into a builder attr.)

FallbackDir: Use VecBuilder for orports

2022-05-04T16:18:55Z

And drop the ad-hoc orport() method. This brings FallbackDir's orports field in line with our list builder API. The general semver note in "configuation" seems to cover most of this.

FallbackDir: Do orport validation after autogenerated build

2022-05-04T16:18:55Z

This avoids it having to recapitulate defaulting logic.

FallbackDir: Do not consider defaulted-empty orport list to be valid

2022-05-04T16:18:55Z

fallback list: Introduce and use FallbackListBuilder

2022-04-22T16:48:03Z

Now the network fallbacks configuration wants to Deserialize a Vec, rather than validated Vec. Methods on FallbackListBuilder are as per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/462#note_2797697 mutatis mutandi for the fact that this struct has only fallbacks in it.

fallback list: Move default list into tor-guardmgr

2022-04-22T16:39:58Z

This is where the FallbackList type is. We are going to want to provide a builder too, which ought to impl Default. This means that the default value for the type must be next to the type. In any case, it was anomalous that it wasn't. This commit is pure code motion.

Rename fallback::status::Status to DirStatus.

2022-04-04T16:31:41Z

It's about to be shared between fallbacks and guards.

Fix some Rustdoc links.

2022-03-30T14:41:40Z

Refactor FirstHopId into type-differentiated form

2022-03-30T14:41:39Z

The FirstHopId type now records an enum that stores whether the hop is a guard or a fallback. This change addresses concerns about remembering to check the type or source of an Id before passing it down to the FallbackState or GuardSet. Making this change required an API change, so that dirmgr can report success/failure status without actually knowing whether it's using a fallback or a guard.