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

release: Bump all tor-/arti- crates to 0.31.0.

2025-06-05T10:33:57Z

This was done using: for crate in $(./maint/list_crates | grep -P '^tor-|^arti-'); do cargo set-version -p $crate 0.31.0 done

*: 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.

./maint/cargo_sort: Run cargo-sort on the entire workspace.

2025-05-27T13:32:26Z

The [latest version] of `cargo-sort` is more opinionated than the previous one, and is now causing the `rust-checks` job to fail on `main`. This commit applies the fixes needed to satisfy the new `cargo-sort` rules. These changes were generated by running `cargo sort --workspace` several times, until `cargo sort --check --workspace` finally succeeded (it couldn't fix all the errors in one go, for some reason). I have omitted the changes `cargo-sort` made to the top-level `Cargo.toml`, to preserve the topological ordering of the workspace members. Closes #2014 [latest version]: https://github.com/DevinR528/cargo-sort/blob/f066ae80e5e6f5c1d8f0e2b8099461dcb97d9656/changelog.md#200

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.