mirrors/arti.git/crates/tor-circmgr/src, branch arti-v1.4.4

*: suppress cognitive_complexity warnings from nightly

2025-05-29T14:21:17Z

Apparently clippy nightly is better (or worse?) about detecting complex functions than before, so I'm suppressing these warnings where they occur. I have mixed feelings about these warnings: On the plus side, they really do help to detect functions that are twistier than they need to be. On the minus side, they get confused by tracing macros, and the "allows" do pile up. But on the plus side, those "allows" do provide a way to find functions that need to be refactored, and they are never uglier than the functions they decorate.

hspool: Explain _why_ ClientRend is Guarded.

2025-05-22T16:26:16Z

(text from Gabi)

hspool: refactor path match to be exhaustive.

2025-05-22T16:02:30Z

hspool: ClientRend first should be Guarded

2025-05-22T16:02:30Z

On !3007, @gabi-250 says that it was a mistake to have it be Naive.

Apply 1 suggestion(s) to 1 file(s)

2025-05-22T15:11:28Z

Co-authored-by: gabi-250

circmgr: Apply last-hop-in-stem usage when retrieving a stem circ.

2025-05-20T20:15:05Z

Closes #1911.

circmgr: when building client rend stems, make sure last hop has new_rend usage.

2025-05-20T19:22:08Z

guardmgr, circmgr: Make vanguard selection take a RelaySelector.

2025-05-20T19:22:08Z

This is the preferred type for choosing a relay, since unlike a RelayExclusion, it lets us add multiple restrictions, and a relay usage.

circmgr: Propagate Option down to path selection functions

2025-05-20T19:22:08Z

We'll need this in order to build paths that are specifically for client rend circuits. I thought of using a boolean here, but that had potential to get ugly in the future.

circmgr: Change get_or_launch_stem to take a HsCircKind

2025-05-20T19:22:08Z

We're going to be looking at this a little more closely in order to decide whether the last hop of a stem can be used as a rendezvous point.