mirrors/arti.git/crates/tor-proto/src/circuit, branch arti-v2.5.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.02026-06-29T13:52:57Zproto: Add expect(unused) where needed2026-06-29T13:52:57ZGabriela Moldovangabi@torproject.org2026-06-23T18:00:55Zurn:sha1:4f4130c34ffb89ff4c75c143d1612d2ced60e9d6
Now that relays no longer use `CtrlCmd::AwaitStreamRequests`, some of
these fields are unused. I'm leaving them in for now, but we should
remove them if they're still unused after we finish the circ reactor
impl.
I'm not removing `AwaitStreamRequests`, because it will be needed by
onion services, when we replace the old client circuit reactor with the
new one.
proto: Support passing a stream request filter to the reactor2026-06-29T13:50:49ZGabriela Moldovangabi@torproject.org2026-06-12T10:03:02Zurn:sha1:60306abe64f00e5053c2728e4c884a6e3ff714b4
Relay circuits always need a filter, so it's best to set it via the
constructor.
Part of #2582
Closes #2577
tor-proto: pass correct chan msg cmd to `decrypt_outbound()`2026-06-24T17:09:18ZSteven Engleropara@torproject.org2026-06-24T15:16:49Zurn:sha1:9f335acf7b0426fba583a68ab4b15d25cc6d9531
Instead of converting the `RelayEarly` message to a `Relay` message, we
add a new `RelayMaybeEarlyChanMsg` restricted message set that can hold
either.
Previously we were passing the wrong channel message command to
`decrypt_outbound()`, which would cause the decryption to fail for relay
crypto algorithms that use the command.
proto: Rename LocalApplicationStream for clarity2026-06-23T15:58:29ZGabriela Moldovangabi@torproject.org2026-06-23T15:47:44Zurn:sha1:d5815e8b4834d76b6831e0451322a6d55c3e3e66
See
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4139#note_3429586
proto: Rework error handling in `HopMgr::get_or_spawn_reactor()`2026-06-23T15:58:29ZGabriela Moldovangabi@torproject.org2026-06-22T17:14:39Zurn:sha1:d6d24bc58609d0cf6c011d70b4906ad4dc7ca2fa
This reworks `get_or_spawn_reactor()` to return `Error` instead of
`ReactorError`.
The main change here is that we now have a dedicated `Error::Spawn`
variant for `SpawnError`s, instead of mapping these to `ReactorError`
(which actually triggers a clean shutdown, which is not quite what we
want here).
proto: Simplify StreamEvent::LocalStreamClosed (fmt)2026-06-23T15:58:29ZGabriela Moldovangabi@torproject.org2026-06-22T16:29:43Zurn:sha1:878a93d292fa4dcdeb3c8e781f563ff2fa00949eproto: Simplify StreamEvent::LocalStreamClosed2026-06-23T15:58:29ZGabriela Moldovangabi@torproject.org2026-06-22T16:28:43Zurn:sha1:e6df68625731c3798e027afd8f6f19c17520f1d1
This doesn't need to contain the `CloseStreamBehavior` or
`TerminateReason`, because we always use the same ones.
proto: Rename StreamEvent::Closed to LocalStreamClosed2026-06-23T15:58:29ZGabriela Moldovangabi@torproject.org2026-06-22T16:25:16Zurn:sha1:eb5507f8829b016bc99d7bb326540aac9f3b0cca
I realized the previous naming was ambiguous. Hopefully this makes it
clear that this `StreamEvent` triggers when the MPSC channel connecting
the reactor to the local application stream (for example the local TCP
connection of the stream, in the case of exit streams) is dropped.
proto: Implement ClosePendingStream in the stream reactor2026-06-23T15:58:29ZGabriela Moldovangabi@torproject.org2026-06-22T10:29:59Zurn:sha1:205e03d38ea538522a5acf0fba8020199a818c6a
Closes #2590
proto: Add a helper function for handling closed streams (fmt)2026-06-23T15:58:29ZGabriela Moldovangabi@torproject.org2026-06-22T15:51:14Zurn:sha1:c41555a976937d40e7f14720384bb43331e8a02e