mirrors/arti.git/crates/tor-circmgr, branch arti-v1.8.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.02025-12-02T11:07:59ZBump all the unstable tor- and arti- crates to 0.37.0.2025-12-02T11:07:59ZGabriela Moldovangabi@torproject.org2025-12-02T10:58:54Zurn:sha1:e7d740eda02e05dd53574b6753cc4b45ab160b58
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.37.0
done
circmgr: Add missing docs for RestrictionFailed2025-12-01T11:03:59ZGabriela Moldovangabi@torproject.org2025-12-01T11:03:59Zurn:sha1:d28e1ad81d437973420be3bf05487aa61e6df3e0circmgr: allow unstable_name_collisions lint for exactly_one()2025-12-01T10:59:32ZGabriela Moldovangabi@torproject.org2025-12-01T10:59:32Zurn:sha1:c62f86e5310379299f57d780d089967f29c0d919
This silences a new nightly warning.
tor-circmgr: simplify `CircMgrConfig`2025-11-26T05:40:41ZSteven Engleropara@torproject.org2025-11-26T05:40:37Zurn:sha1:364db06a741e717d5d0b213dc79dfbad66fc6ca1
Now that `vanguard_config()` is no longer conditional, we can handle
`vanguard_config` just like other accessors. This is a breaking change,
but I think we may as well make this change while we've already made
another breaking change in the previous commit.
tor-circmgr,arti-client: `CircMgrConfig::vanguard_config` is always built2025-11-26T05:31:15ZSteven Engleropara@torproject.org2025-11-26T05:10:39Zurn:sha1:c7ba4af1b4ee12591af0034fee0c02a4475f4821opentelemetry: Instrument a bunch of functions.2025-11-24T16:28:07ZWesley Aptekar-Casselsme@wesleyac.com2025-11-24T16:28:07Zurn:sha1:a4db6a7495b13dd7b00416dd1660a5ad82b60919
These are all aimed at figuring out in more detail what's going on
in #2079 and related issues.
tor-circmgr: fix incorrect match on `HsOnly`2025-11-20T01:37:55ZSteven Engleropara@torproject.org2025-11-20T01:33:59Zurn:sha1:45a3dffa8678f17d4d01f645bc119b7f1b898906
Rust was treating this as a wildcard match if the `hs-common` feature
wasn't enabled. This shouldn't have caused any bugs since the other
match arms were already exhaustive, but this could have lead to a bug if
new enum variants were added to `SupportedTunnelUsage`.
```text
warning: variable `HsOnly` should have a snake case name
--> crates/tor-circmgr/src/usage.rs:600:13
|
600 | HsOnly => {
| ^^^^^^ help: convert the identifier to snake case: `hs_only`
|
= note: `#[warn(non_snake_case)]` (part of `#[warn(nonstandard_style)]`) on by default
warning: `tor-circmgr` (lib) generated 1 warning
```
RelayFlags: Use RelayFlag enum variant names everywhere2025-11-18T19:50:23ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-18T18:55:10Zurn:sha1:c37e44403416b7f1abbd62d080b698da35d04537
Abolish the constants with the transitional names.
This also abolishes the controversial name `H_S_DIR`, which Rust case
transformation rules generated from `HSDir`.
RelayFlags: Use the singular RelayFlag for naming individual flags2025-11-18T19:44:21ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-18T18:36:08Zurn:sha1:3245738729e1d93be48485f2877a9e17ba2e7f28
We're going to separate RelayFlag from RelayFlags.
We could continue to provide a bunch of constant values for
RelayFlags, for each individual type, but that would involve an ad-hoc
derive, and would still be a bit of an unusual API.
Instead, we're going to make ``RelayFlag` a normal enum.
In this commit, we change everyone to refer to it by its singular
name. Hopefully separating out this bulk change makes both this, and
the core commit, easier to review.
tor-netdoc: Remove the RelayFlags type alias in netstatus2025-11-18T17:06:51ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-10T14:52:43Zurn:sha1:3ecd75a43c41a57288abe0a7da23a80ec89d23e0
I would do `#[deprecated]` but empirically that has no effect...