mirrors/arti.git/crates/tor-circmgr/src/path.rs, branch arti-v2.5.1

opentelemetry: Instrument a bunch of functions.

2025-11-24T16:28:07Z

These are all aimed at figuring out in more detail what's going on in #2079 and related issues.

tor-linkspec: Change HasAddrs::addrs to return an Iterator

2025-10-06T18:52:44Z

This will let us model the actual structure of routerstatus entries in netdocs more closely. They don't have the addresses in a single list. When this code was written this would have been much more awkward, but now we have RPITIT.

Move `FallbackDir` into `tor-dircommon`

2025-09-11T17:53:40Z

circmgr: Don't count channel negotiation towards circuit built time.

2025-08-07T22:05:38Z

This is important, since some circuits require us to negotiate a new channel, and some don't: by adding this variability, we can easily learn a timeout based on pre-existing channels to our guards, but then later time out if it takes a while to open a TLS connection. This is a possible solution to part of #2079, a bug where we "learn" a circuit timeout that is too low for us to satisfy.

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.

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.

tor-circmgr: removed unused "chosen exit" functionality

2024-08-15T17:54:58Z

tor-circmgr: fix flaky `path::exitpath::test::by_ports` test

2024-08-13T18:44:24Z

The `path::exitpath::test::by_ports` test sometimes failed now that the test is using a `GuardMgr` since `select_guard`, when given a chosen exit, only ensures that the guard and chosen exit are not in the same family. It does not ensure that the guard and exit do not share an extended family. This commit relaxes an assertion in the test. ```text thread 'path::exitpath::test::by_ports' panicked at crates/tor-circmgr/src/path/exitpath.rs:295:9: assertion failed: r1.can_share_circuit(r3, subnet_config) ``` This "chosen exit" functionality isn't actually being used anywhere (`ExitPathBuilderInner::ChosenExit` is only ever constructed in tests).

tor-circmgr: make `GuardMgr` mandatory

2024-08-13T00:21:53Z

Functions that took `Option<&GuardMgr>` now take only `&GuardMgr`. Three unit tests were removed that covered behaviour when no guard manager was set.

tor-circmgr: Add a TODO about an unused restriction.

2024-06-20T12:12:55Z