mirrors/arti.git/crates/arti-client, branch arti-v1.2.4

Bump all the unstable tor- and arti- crates to 0.19.

2024-06-05T15:06:54Z

The unstable crates are: - tor-error - tor-config - tor-units - tor-geoip - tor-rtcompat - tor-rtmock - tor-log-ratelim - tor-rpcbase - tor-memquota - tor-llcrypto - tor-protover - tor-bytes - tor-hscrypto - tor-socksproto - tor-checkable - tor-cert - tor-linkspec - tor-cell - tor-proto - tor-netdoc - tor-consdiff - tor-netdir - tor-relay-selection - tor-persist - tor-chanmgr - tor-ptmgr - tor-guardmgr - tor-circmgr - tor-dirclient - tor-dirmgr - tor-keymgr - tor-hsclient - tor-hsservice - tor-hsrproxy - arti-client - arti-rpcserver - arti-hyper - tor-basic-utils - tor-async-utils Done using ``` for p in "${unstable[@]}"; do cargo set-version -p $p 0.19; done ``` where `unstable` contains the list above

arti-client: Unconditionally retire all HS circuits if circmgr says so.

2024-06-03T14:28:23Z

If the circmgr retires all of its circuits, so should the HS circ pool. The circuits can be retired for various reasons (for example, if the configured vanguard mode changes).

arti-client: Add TODO about always clearing the HS circ pool.

2024-06-03T14:28:23Z

tor-circmgr: Remove VanguardMode from Pool (fmt).

2024-06-03T14:28:22Z

tor-circmgr: Remove VanguardMode from Pool.

2024-06-03T14:19:24Z

Storing the VanguardMode in multiple places (in the VanguardMgr *and* the HS circ Pool) is dangerous and can lead to split brain situations where different parts of the code think they are running in different VanguardModes. See #1424

tor-guardmgr: Unconditionally define VanguardConfig.

2024-06-03T09:47:32Z

We want to export the `VanguardConfig` even if the `vanguards` feature is disabled (we will need to unconditionally include it in the arti config). Note that if `vanguards` are disabled, the `VanguardMode` from the `VanguardConfig` can only be `Dsiabled`.

arti-client: Remove unnecessary VanguardConfig pub use.

2024-06-03T09:47:32Z

This is already exported via the `pub mod vanguards` module, so there is no need to export it from the top-level too. This *is* a breaking change, but the downstream fix is trivial (and the type should never have been exported directly from `arti_client::config` in the first place).

RPC: Require an Error type in methods.

2024-05-16T12:40:06Z

This is needed so that we can cast special methods' return types properly. I wish I could make this optional, but Rust doesn't allow defaulting an associated type.

Merge branch 'enforce_method_names' into 'main'

2024-05-16T11:53:54Z

RPC: Enforce method name format. Closes #823 See merge request tpo/core/arti!2149

arti-client: Add one-hop circuit example

2024-05-15T10:48:01Z

Co-authored-by: gabi-250