mirrors/arti.git/crates/arti-client/src, branch arti-v1.1.5

Refactor ClientCirc APIs to use Arc.

2023-05-16T13:02:09Z

Now ClientCirc is no longer `Clone`, and the things that need it to be `Clone` instead return and use an Arc We're doing this so that ClientCirc can participate in the RPC system, and so that its semantics are more obvious. Closes #846. Thanks to the type system, this was a much simpler refactoring than I had feared it would be.

RPC: Start on plumbing TorClient into our RPC code

2023-05-04T14:35:03Z

Because of #837, we won't be able to work with _every_ TorClient, so I'm only going to be using TorClient for now.

arti-client: Only run BridgesConfig doc test if pt-client feature is enabled.

2023-05-02T13:10:15Z

One of the tests run as part of `cargo test -p arti-client` fails because the `pt-client` feature is not enabled by default: ``` failures: ---- src/config.rs - config::BridgesConfig (line 221) stdout ---- error[E0432]: unresolved import `arti_client::config::pt` --> src/config.rs:225:26 | 7 | use arti_client::config::pt::ManagedTransportConfigBuilder; | ^^ could not find `pt` in `config` error[E0599]: no method named `bridges` found for mutable reference `&mut BridgesConfigBuilder` in the current scope --> src/config.rs:233:19 | 15 | builder.bridges().bridges().push(bridge_1); | ^^^^^^^ private field, not a method error[E0599]: no function or associated item named `default` found for struct `BridgeConfigBuilder` in the current scope --> src/config.rs:236:48 | 18 | let mut bridge2_builder = BridgeConfigBuilder::default(); | ^^^^^^^ function or associated item not found in `BridgeConfigBuilder` error[E0599]: no method named `bridges` found for mutable reference `&mut BridgesConfigBuilder` in the current scope --> src/config.rs:247:19 | 29 | builder.bridges().bridges().push(bridge2_builder); | ^^^^^^^ private field, not a method error[E0599]: no method named `transports` found for mutable reference `&mut BridgesConfigBuilder` in the current scope --> src/config.rs:255:19 | 37 | builder.bridges().transports().push(transport); | ^^^^^^^^^^ method not found in `&mut BridgesConfigBuilder` error: aborting due to 5 previous errors Some errors have detailed explanations: E0432, E0599. For more information about an error, try `rustc --explain E0432`. Couldn't compile the test. failures: src/config.rs - config::BridgesConfig (line 221) test result: FAILED. 5 passed; 1 failed; 3 ignored; 0 measured; 0 filtered out; finished in 2.10s ``` This disables the `BridgesConfig` doc test if the `pt-client` feature is not enabled. Closes #843 Signed-off-by: Gabriela Moldovan

Merge branch 'plumb' into 'main'

2023-03-30T16:20:54Z

More plumbing for hs connections See merge request tpo/core/arti!1098

Run rustfmt

2023-03-30T14:58:47Z

Apply this churn, which I deferred for ease of review.

arti-client: Call HsCircPool::launch_background_tasks

2023-03-30T14:58:09Z

I found that I had the bug where I forgot to call this function, and reached bad_api_usage!("The circuit launcher wasn't initialized") The possibility of such a bug is a hazard of this API pattern.

tor-hsconn: Rename ConnError (from HsClientConnError)

2023-03-30T14:49:07Z

The old name was unwieldy and other crates can just as well name it by the crate scope.

arti-client: When making hs conn, wait for bootstrap

2023-03-30T14:49:07Z

Not doing this was a bug. The bug was possible because of some code duplication between the exit and hs paths. Add a comment about that.

tor-client: Pass a netdir for each request

2023-03-30T14:49:07Z

This will be more convenient inside tor-hsclient. In arti-client, this mirrors the way TorClient::get_or_launch_exit_circ works.

Move functionality from tor_basic_utils to tor_async_utils

2023-03-29T17:57:11Z

This commit is mostly code movement; I'd recommend reviewing it with git's `--color-moved` option.