mirrors/arti.git/examples, branch arti-v1.5.0

Fix complaints from "cargo sort"

2025-08-27T16:43:24Z

Run "fixup-features"

2025-08-27T16:42:44Z

Update webpki-roots dependency to 1.0.2

2025-08-26T19:39:41Z

proto: Move the `stream` module under `client` (breaking).

2025-08-18T16:09:04Z

The `stream` module is client-specific, for the most part, so I am moving it under `client`. Later on, we will factor out the parts that can be shared with the relay implementation. Note: this is a breaking change as the deleted `stream` module was `pub`. We could've kept the module and reexported from it the public types from `tor_proto::client::stream`, but I think it's better to have this `client` namespacing, because it makes the separation between the client and relay parts clearer.

hyper-examples: Run rustfmt

2025-08-11T12:05:05Z

Merge branch 'main' into !2941

2025-08-11T11:57:22Z

Conflicts: examples/hyper/hyper-http-client-example/Cargo.toml examples/hyper/hyper-http-hs-example/Cargo.toml In both cases, just the change of edition, which I have applied to examples/hyper-examples/Cargo.toml instead.

Switch Cargo.toml files to edition 2024.

2025-08-07T15:28:36Z

First, run ``` git grep -l "^edition =" | xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;' ``` Second, manually verify that all Cargo.toml files have changed, and nothing else has changed. Third, run cargo fmt again.

obfs4-checker: do not enable tor-proto/experimental.

2025-08-06T15:55:19Z

1. In general, it is always wrong to unconditionally depend on "experimental". Instead, a crate should depend on the particular experimental features it needs (if any). 2. obfs4-checker does not appear to need tor-proto/experimental any longer.

proto: abolish path_ref() in favor of all_paths().

2025-08-05T18:23:02Z

Until now, we've been using `ClientCirc::path_ref()` to get the *only* path of a circuit. Now that `ClientCirc` is a handle to a tunnel reactor (which may or may not be multi-path), we need to decide for each call site of `path_ref()`, if we actually want *all* paths in the tunnel, or if we expect the tunnel to be single-path and thus want the *only* path in the tunnel. I've added two new APIs to address this: `all_paths()`, for getting all the paths in the tunnel, and `single_path()` for getting the only path in the tunnel, or an error if the tunnel is single-path.

arti-client: Use the new Tunnel interface

2025-08-05T18:23:02Z

Signed-off-by: David Goulet