mirrors/arti.git/crates/tor-proto/src/client.rs, branch mainmirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=main2026-07-30T21:34:23Ztor-cell: rename `XonKbpsEwma` to `XonKBpsEwma`2026-07-30T21:34:23ZSteven Engleropara@torproject.org2026-07-30T21:01:27Zurn:sha1:0fecfa9a0102ff58676bcb0c5e36eed4996a68f4multiple crates: Fix clippy warnings2026-07-10T14:50:50Zhjrgrn3874-hjrgrn@gitlab.torproject.org2026-07-10T14:12:44Zurn:sha1:c1a50610f1fd134b16792ba32b30eb03a7e6b666proto: Add crate-level exports for two extra stream types (fmt)2026-06-17T13:38:44ZGabriela Moldovangabi@torproject.org2026-06-17T13:31:26Zurn:sha1:d305c6c0a201703ce14fbcfdce1864aeda9cc8dctor-proto: destructure the `ReactorStreamComponents`2026-05-21T16:35:59ZSteven Engleropara@torproject.org2026-05-21T15:23:52Zurn:sha1:4c1ddd2de31ff622d0244f5456527fe035e467aetor-proto: have `StreamReqInfo` store a `ReactorStreamComponents`2026-05-21T16:35:59ZSteven Engleropara@torproject.org2026-05-21T15:13:07Zurn:sha1:3ae295c879f773b8c6e922436fb96c020777555ator-proto: move more stream queue init to reactor2026-05-21T16:35:59ZSteven Engleropara@torproject.org2026-05-21T01:57:13Zurn:sha1:e62d824614fc501d21f6b58f1e98346bf495e1e3
Previously when initializing a stream, we constructed most of the
stream-related queues outside of the reactor and passed the relevant
halves of the queues (senders or receivers) into the reactor.
A downside of the above approach is that the reactor may be better
informed about what queues to construct, and how to construct them. For
example the reactor knows what type of flow control that the hop is
using, so it knows whether we need queues for passing rate limits and
drain rates for XON/XOFF flow control.
This commit moves the construction of these queues into the reactor and
passes the relevant halves out of the reactor. In the future we can make
better decisions about which queues are needed depending on the flow
control method used instead of always constructing them (see arti#2068).
Reviewing with `--color-moved` might be helpful as a few lines have been
moved.
tor-proto: add `ReactorStreamComponents` to bundle return vals2026-05-21T01:52:49ZSteven Engleropara@torproject.org2026-05-20T19:29:58Zurn:sha1:2801a1b30f50488ca79bbe21d3061b07fe40b945tor-proto: move stream incoming queue init to reactor2026-05-21T00:36:59ZSteven Engleropara@torproject.org2026-05-12T22:36:57Zurn:sha1:be505ab176da88dd8cea7e3a42530d81fb0267b5
The stream queue length (for messages incoming from the Tor network)
depends on the type of flow control we're using for the hop. Currently
we construct the stream queue outside of the circuit reactor, but we
don't have the flow control information here.
Instead of constructing the stream queue outside of the reactor and
passing the sender into the reactor, we construct the stream queue
inside of the reactor and pass the receiver out of the reactor.
proto rpc: Turn tunnel paths into a dict2026-04-28T18:13:39ZNick Mathewsonnickm@torproject.org2026-04-21T13:45:57Zurn:sha1:9b25ca54c6f00bd8da27d6d8295d7cb0c4e869ee
This will make it possible to tell whether a path has been replaced
in the tunnel.
Since the UniqId type might change its representation in the future,
I've documented that we don't guarantee anything about the strings
used to distinguish paths.
proto: Add an RPC function to access tunnel and inspect its path.2026-04-28T18:13:39ZNick Mathewsonnickm@torproject.org2026-04-08T20:10:01Zurn:sha1:b976186994f3e8e7b6fa30c03516e08880ad9323
Additionally, allow inspecting tunnel paths directly from streams.