mirrors/arti.git/crates/tor-proto/src/client/reactor.rs, branch arti-v2.3.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.3.02026-04-06T15:00:29Ztor-proto: lower log level of "removing circuit leg"2026-04-06T15:00:29ZSteven Engleropara@torproject.org2026-04-06T15:00:14Zurn:sha1:0d347458b98e4f91b3f8194a8e0829331bd72223
This appears often in the arti logs, but is a normal thing to happen.
Fix word duplicate typos2026-03-15T20:18:56ZTobias Stoeckmanntobias@stoeckmann.org2026-03-15T20:05:34Zurn:sha1:2173207d8b909d1afdc55adda13faac13cdded0fproto: Replace CircSyncView with previously client-only CircSyncView2026-02-16T15:24:51ZGabriela Moldovangabi@torproject.org2026-02-16T10:58:35Zurn:sha1:863ee4fe98b66d0dd8c7c53f98a6ab1c2ff347f2
Note: this commit only contains the removal of the old `CircSyncView`,
and it of course doens't compile. A future commit will replace the
removed file with the `syncview.rs` from the client module.
This change is split over two commits because it makes reviewing easier
(`git mv`ing the new file over the old results in a confusing diff,
because `git` refuses to show it as a move).
proto: Factor ReactorResultChannel into the shared reactor module2026-01-29T16:33:21ZGabriela Moldovangabi@torproject.org2026-01-21T14:16:16Zurn:sha1:5bc82538b484986c031a56766797a8a573c09641
This is not just for clients!
proto: Move TimeoutEstimator to util2026-01-29T16:33:21ZGabriela Moldovangabi@torproject.org2026-01-12T10:44:05Zurn:sha1:5c5bf40652f00fff3205fc5a2ff44ad48e96b8de
This will be used in the stream reactor too (and the stream reactor will
eventually replace the corresponding client impl).
proto: Dedupe IncomingStreamRequestHandler2026-01-12T19:10:54ZGabriela Moldovangabi@torproject.org2026-01-12T18:50:26Zurn:sha1:271603e38f5be23ae3ff756a18fb87406a933e9dproto: Add an immediate order for client CircuitEvent ordering2025-12-10T16:04:26ZDavid Gouletdgoulet@torproject.org2025-12-10T15:25:01Zurn:sha1:a448ab20270f8637d3f34b2af363453fefd621f5
With a protocol violation, we have to immediately deal with such event
before emitting anything on the wire.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Rename CircuitAction and cie to CircuitEvent2025-12-10T16:04:26ZDavid Gouletdgoulet@torproject.org2025-12-10T15:20:41Zurn:sha1:7e69f0b2d31acfad14c3d046e89f8633626785f8
This mirrors also the relay reactor. We've introduced the ProtoViolation
into a previous commit which is not an action but rather an "event" that
happened on a circuit.
And so, better semantic. No behavior change.
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Rename Circuit{Action/Event}::Shutdown to ProtoViolation2025-12-10T16:04:26ZDavid Gouletdgoulet@torproject.org2025-12-10T14:24:59Zurn:sha1:1c97ec8836f227209e8dbc19253afcbe1f9e2610
Signed-off-by: David Goulet <dgoulet@torproject.org>
proto: Client circuit reactor now handles AnyChanMsg2025-12-10T16:03:12ZDavid Gouletdgoulet@torproject.org2025-12-08T19:16:33Zurn:sha1:d5ad6142db84d917f0035060f92678da3ba98ee1
This commit removes the CircuitRx* based solely on the client circuit
message and moves it into the top level of the crate so all reactors can
use them.
The client reactor then upon receiving the message, it converts the
AnyChanMsg into a ClientCircChanMsg. On error, this leads to a shutdown
of the entire reactor due to a fatal error.
In order to pull this off, we added a CircuitAction::Shutdown that is
handled as a priority.
Signed-off-by: David Goulet <dgoulet@torproject.org>