mirrors/arti.git/crates/tor-relay-selection/src, branch arti-v1.5.0

Switch Cargo.toml files to edition 2024.

2025-08-07T15:28:36Z

First, run ``` git grep -l "^edition =" | xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;' ``` Second, manually verify that all Cargo.toml files have changed, and nothing else has changed. Third, run cargo fmt again.

Temporarily suppress mismatched_lifetime_syntaxes.

2025-07-07T15:50:04Z

See #2060.

Improve descriptions of rejected relays: omit "rejected 0/X"

2025-06-25T13:26:00Z

Now instead of saying "rejected 0/40 as not usable as middle relay; 28/40 as in same family as already selected", we say "rejected 28/40 as in same family as already selected". Closes #2006.

tor-relay-selection: Removed dependency on `once_cell`

2025-06-15T02:11:18Z

- Replaced `once_cell::sync::Lazy` with `std::sync::LazyLock`. Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>

relay-selection: Rename RendPoint usage to NewRendPoint.

2025-05-20T19:22:08Z

This mirrors NewIntroPoint, and helps us to remember that we only want to use this usage when we're a client that's picking a rendezvous point; we don't want to enforce it when we're a relay connecting to a client-selected rendezvous point.

relay-selection: tweak messages about rejection reasons

2025-05-20T19:22:08Z

"Useless as xyz" implies that the relay wouldn't work at all as a middle relay, but that's not true: it _would_ work somewhat, but be can't use it for some other reason.

netdir, relay-selection: require Fast and Stable for rendpoints.

2025-05-20T19:22:08Z

Since we don't know what kind of traffic we'll use a rendezvous point for, we don't want to use it if it isn't "Fast" (reasonably high bw) and "Stable" (unlikely to crash soon).

hs: Prevent a client from using a `MiddleOnly` relay for onion services

2025-05-20T19:22:08Z

> The actual impact of this patch is to prevent usage of MiddleOnly > relays as Introduction Points. The Rendezvous Point logic isn't > hooked up yet - nick

netdir: Consider RelayFamilyIds based on family rules

2025-02-25T14:29:50Z

This implements the client side of proposal 321. It's a breaking change in netdir, since in_same_family now takes an extra argument.

relay-selection: Add FamilyRules to exclude_relays_in_same_family.

2025-02-25T14:29:50Z

When we're trying to exclude relays by family, we need to know which lists to look at. This information ultimately comes from the network parameters. We could avoid this change if we just told clients "look at all family information all the time", but that's not what the proposal says. This is a breaking change.