mirrors/arti.git/crates/tor-proto/src/channel/circmap.rs, branch arti-v1.5.0

proto: Rename the `tunnel` module to `client`.

2025-08-18T16:09:04Z

The implementation from `tunnel` is client-specific, so we are renaming the module accordingly. The more generic parts will be pulled into a separate module in a future commit.

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.

proto: temporarily suppress warning; see #2003.

2025-05-16T01:38:25Z

squash! Upgrade rand dependency to 0.9.

2025-03-18T16:09:44Z

- The rand::distributions module has been renamed to rand::distr

tor-proto: Add a tunnel module.

2025-02-20T20:15:12Z

Move StreamTarget to the tunnel module and the circuit module. From now on streams will be implemented on tunnels, not circuits. This moves `StreamTarget` to the tunnel module. A future change will replace `ClientCirc` with `ClientTunnel` inside `StreamTarget`. This is mostly code motion, best reviewed with `--color-moved`. Signed-off-by: David Goulet

tor-proto: Specify which of the 2 senders is used for sending cells.

2024-11-20T10:53:24Z

Apply deferred rustfmt churn

2024-10-09T17:21:09Z

memquota: Use an mq_queue for channel->circuit RX queue

2024-10-09T17:19:41Z

Fixes #1682. (This involves some noise in the tests.)

memquota: Introduce type aliases for channel->circuit RX queue

2024-10-09T17:19:38Z

This is neater and will make changing the type (in a moment) less noisy.

extract tor_async_utils::oneshot into ::oneshot-fused-workaround

2024-08-28T14:27:46Z

Having this in the `tor-async-utils` crate prevents us from doing both of the following without introducing a circular dependency: * using it in `tor-rtmock` (which we currently do, particularly in tests). * using `tor-rtmock` to test things in `tor-async-utils`. We don't do this yet, but it is generally sensible to do so. In particular we want to move the `stream_peak` module there, which is currently tested with `tor-rtmock`. Moving this into its own crate avoids this circular dependency.