mirrors/arti.git/crates/tor-proto/src/tunnel/reactor.rs, branch arti-v1.4.5

tor-proto: Remove unnecessary return.

2025-07-07T15:58:27Z

proto: Continue reading from leaky-pipe streams if main leg is blocked.

2025-06-27T14:16:16Z

Addresses https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3077#note_3218281

hsservice: Stop using HopNum and use TargetHop

2025-06-26T14:18:30Z

This requires some changes to the tor-proto crate to handle the inbound TargetHop from the HS subsystem and then resolve it into a HopNum for a single circuit. It is expected that this will change again with Conflux to only use HopLocation internally in a Tunnel and then use HopNum into a Circuit. Signed-off-by: David Goulet

hs: Remove the use of HopNum and instead use TargetHop

2025-06-26T14:18:30Z

This is in the spirit of making everything going inbound the tor-proto crate to use a TargetHop. This becomes much easier for the HS subsystem as it only uses the last hop for its conversation and setup. Signed-off-by: David Goulet

proto: Add helper function to resolve TargetHop

2025-06-26T14:18:30Z

The Reactor has two functions to resolve both TargetHop into a HopLocation and then a HopLocation into a (UniqId, HopNum). This commit simply adds a helper that does both but returns an Option instead of a Result as it will be used by the reactor command handler and more in future conflux commits. Signed-off-by: David Goulet

tor-proto: Give Circuit a handle to the DynTimeProvider.

2025-06-23T16:48:44Z

This will enable us to replace the calls to `Instant::now()` with `DynTimeProvider::now()` throughout the RTT estimator. This gives us the ability to mock the time, and test that conflux leg switching occurs as expected.

tor-proto: Replace LegId/LegIdKey with UniqId.

2025-06-13T16:13:45Z

Closes #1999

tor-proto: Give ConfluxSet a TunnelId for logging purposes.

2025-06-13T10:54:52Z

tor-proto: Use TunnelScopedCircId instead of UniqId for logging.

2025-06-12T18:02:30Z

tor-proto: Assign a separate identifier to the tunnel reactor.

2025-06-12T18:02:30Z

The plan is to reuse this identifier for the future tunnel reactor updates channel (a channel for sending tunnel status updates to a central consumer).