mirrors/arti.git/crates/tor-proto/src/client/reactor/circuit, branch main

tor-proto: disable flowctrl sidechannel mitigations for relays

2026-08-19T17:29:14Z

The end result should be: 1. outgoing streams - enable sidechannel mitigations 2. incoming hs streams - enable sidechannel mitigations 3. incoming exit streams - disable sidechannel mitigations

proto: Add {backward|forward} prefix to circ_id in logs

2026-08-03T18:27:50Z

Signed-off-by: David Goulet

proto: Rename uniq_id to circ_unique_id mostly in logging

2026-08-03T18:27:50Z

We have decided that instead of "uniq_id" in logging, we'll use the "-[]-id" syntax to indicate who is that unique ID. This commit only renames circuit's unique ID to "circ_uniq_id". Signed-off-by: David Goulet

proto: Log both UniqId and CircId when possible

2026-08-03T18:27:50Z

This commit only affects logging. Whenever possible, log both the UniqId and CircId. This also changes the log lines which is now "uniq_id=" and "circ_id=" as the UniqId is internal and circ_id (CircId) is protocol level. Signed-off-by: David Goulet

tor-cell: rename `XonKbpsEwma` to `XonKBpsEwma`

2026-07-30T21:34:23Z

proto: log hop settings at trace upon client circuit opening.

2026-06-23T13:18:44Z

tor-proto: move memquota stream account arg to last position

2026-05-21T16:35:59Z

This better matches nearby code.

tor-proto: move more stream queue init to reactor

2026-05-21T16:35:59Z

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 vals

2026-05-21T01:52:49Z

tor-proto: move stream incoming queue init to reactor

2026-05-21T00:36:59Z

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.