| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will match our needs better and help avoid some `Arc<>`s.
It will be especially helpful for avoiding `Arc`s we don't
actually have.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I'm using an Arc<[]> here though I think that there's a chance
that a simple Vec<> would suffice. Since it's an internal type,
nothing will break if we change it later.
Also, we now switch into and out of the Bridges guard sample
as needed. However, that selection is not (yet) built from the
list of bridges. That will come soon.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Also fix its behavior when using bridges.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The first part changes which guard set is active based on based on
the parameters, which always come from a NetDir; the second changes
the contents of the active guard set, based on a Universe.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These arguments were used only for legacy (testing) purposes; the
tests now use `TestNetDirProvider`. This lets us simplify our
internal logic for passing a `NetDir` to our samples, and prepare
for having a `BridgeSet` to pass there instead.
This is a breaking change to `guardmgr` and `circmgr`.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I'm about to remove the old testing APIs from GurdMgr that took in a
NetDir in each function: adding this will make that possible.
|
| | | | | | |
|
| | | | | | |
|
| | | |/ /
| |/| |
| | | |
| | | | |
We require these for NetDirProvider, so this shouldn't be a big reach.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Spelling fixes and normalizations on some high-level crates
See merge request tpo/core/arti!835
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | | |
This allows the use of Box<dyn BridgeDescProvider> in callers,
since Box<dyn BridgeDescProvider> is now Clone.
|
| |/ / |
|
| | |
| |
| |
| |
| |
| | |
This was confusing, because it's the output of the donwload, but
nowhere near the output of the whole process. And it's going to
become even less so.
|
| | |
| |
| |
| | |
It deserves this treatment, I think.
|
| | |
| |
| |
| |
| | |
This gives names to things and makes things clearer, and this will be
even more true in a moemnt.
|
| | |
| |
| |
| | |
We're going to want to reuse this for handling cached stuff.
|
| |/ |
|
| |\
| |
| |
| |
| | |
tor-guardmgr: use imported WeightThreshold in one place
See merge request tpo/core/arti!825
|
| | |
| |
| |
| |
| | |
Without this, an unused import warning is generated when building
without features.
|
| | | |
|
| | |
| |
| |
| |
| | |
This will avoid having to make bridge-related trait features in
GuardMgr conditional, which would be non-additive.
|
| | |
| |
| |
| | |
This is the validation which is called for by the documentation.
|
| | |
| |
| |
| |
| | |
It doesn't seem to me like it makes sense to provide the backward
compatibility here.
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
This does involve additional cloning. However, soon it will mean that
we can pass the whole `TorClientConfig` by reference.
|
| |
|
|
| |
These are newly present on 1.65. We can address them later.
|
| | |
|
| |\
| |
| |
| |
| | |
set all crate edition to 2021
See merge request tpo/core/arti!822
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
The RetryDelays are being triggered for the 2nd time here, so their
timeouts can be longer. We must bump the sleep to make sure we don't
have a flaky test.
|
| | |
| |
| |
| | |
Worsify formatting as demanded by rustfmt.
|
| | |
| |
| |
| |
| | |
This involves breaking the calls to `new_bridges.remove` into a helper
that does the logging.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Prior to the previous commit, set_bridges would malfunction if there
were bridges which where (i) in current (ii) in queued or running
(iii) in the new bridge set.
This test failed then and passes now.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This was fundamentally confused and irregular. Now it is more
regular: it does the same things to all the elements of Tracked,
and a simple filtering on current.
This fixes a bug, for which I'm about to add a test case.
|
| | | |
|
| | |
| |
| |
| | |
We'll use this in a moment.
|
| | | |
|
| | |
| |
| |
| |
| | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/820#note_2850269
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
0.99.[012] have a bug https://github.com/JelteF/derive_more/issues/114
which makes the Deref derive for bridgedesc::StateGuard not work
and therefore breaks minimal-versions CI.
It seems simpler to require the newer version everywhere.
|
| | | |
|