mirrors/arti.git/crates/tor-circmgr/src/mocks.rs, branch arti-v2.0.0

circmgr: Implement expiration for long-lived tunnels.

2025-11-12T15:00:55Z

This code uses the algorithm of prop368: When a tunnel is sufficiently isolated, we want to expire it after it has been disused for a certain amount of time. The implementation is a little tricky, since we need to call an async function on ClientTunnel to look up the disused_since() check. We don't want to call async functions while holding locks, so we need to drop the TunnelList lock before we do the disused_since() calls, and the grab it again. As part of this change, I've had made expiration functions return the earliest time at which any tunnel might expire. We can use this in the future to spawn fewer expiration tasks, and scan the list of tunnels less often.

proto: Add a circuit module shared between client and relay impls.

2025-08-28T10:54:48Z

This is just code motion (I suggest reviewing with `--color-moved`). This also moves the implementation-agnostic parts from `tor_proto::client::circuit` to a new `tor_proto::circuit` module.

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.

Do not fully-qualify Sync.

2025-08-05T18:23:03Z

It's necessary and more verbose (and it's rather uncommon).

proto: abolish path_ref() in favor of all_paths().

2025-08-05T18:23:02Z

Until now, we've been using `ClientCirc::path_ref()` to get the *only* path of a circuit. Now that `ClientCirc` is a handle to a tunnel reactor (which may or may not be multi-path), we need to decide for each call site of `path_ref()`, if we actually want *all* paths in the tunnel, or if we expect the tunnel to be single-path and thus want the *only* path in the tunnel. I've added two new APIs to address this: `all_paths()`, for getting all the paths in the tunnel, and `single_path()` for getting the only path in the tunnel, or an error if the tunnel is single-path.

circmgr: Fix unit tests

2025-08-05T18:23:02Z

Signed-off-by: David Goulet

circmgr: Major rename for the new Tunnel namespace

2025-08-05T18:23:02Z

The CircMgr will no longer yield circuits but tunnels (src/tunnel.rs). This is a first step to rename most circuit related objects to use "tunnel" instead. Some "circuit" names have been kept for more precise definitions. No behavior changes. Signed-off-by: David Goulet

tor-proto: Update the TunnelMutableState when a circuit is removed.

2025-05-15T16:33:33Z

This is messy, because `ClientCirc::{path_ref, n_hops, ..}` become fallible (we can't unwrap the result, because when a circuit is closed, its state gets removed from the `TunnelSharedState`, but its `ClientCirc` handle continues to exist, so any attempt to retrieve the state will result in an `Err`).

circmgr: Rename AbstractCirc::{extend_ntor => extend}

2025-04-28T17:29:02Z

We don't want to be thinking about ntor vs ntor3 in circmgr.

circ: Remove CircParameters reference in call stack

2025-04-23T18:36:28Z

This avoids cloning the object and instead allows us to have a CircParameters per hop on the circuit path. This will come handy with congestion control where each hop might have different congestion control parameters. Part of #1817 Signed-off-by: David Goulet