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

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.

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

Typo fixes (automatic and hand-verified)

2025-07-09T16:27:29Z

Made with https://crates.io/crates/typos-cli

examples, fixup-features: use inline vars in format string

2025-05-29T14:21:17Z

Nightly clippy now suggests this.

./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

tor-proto: Update the TunnelMutableState when a circuit is removed.

2025-05-15T16:33:33Z

This is messy, because `ClientCirc::{path_ref, n_hops, ..}` become fallible (we can't unwrap the result, because when a circuit is closed, its state gets removed from the `TunnelSharedState`, but its `ClientCirc` handle continues to exist, so any attempt to retrieve the state will result in an `Err`).

tor-proto: Remove deprecated DataStream API.

2025-02-13T17:51:00Z

Reducing `ClientCirc` proliferation will make our lives easier when implementing !2790.