mirrors/arti.git/crates/tor-proto/src/relay/reactor, branch arti-v1.9.0

proto: Rename Circuit{Action/Event}::Shutdown to ProtoViolation

2025-12-10T16:04:26Z

Signed-off-by: David Goulet

proto: Relay circuit reactor now handles AnyChanMsg

2025-12-10T16:04:26Z

Same as the client reactor, a message outside of our restricted set leads to a reactor shutdown. Signed-off-by: David Goulet

proto: Client circuit reactor now handles AnyChanMsg

2025-12-10T16:03:12Z

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

proto: Move RelayCircChanMsg into relay module

2025-12-10T16:03:12Z

This follows the move of the client specific object. Signed-off-by: David Goulet

proto: Remove incorrect padding logic

2025-12-02T18:46:26Z

This was all wrong, as mentioned in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3487#note_3296033

proto: Add TODO about our TRUNCATE plans

2025-12-02T18:22:25Z

proto: Move EXTEND handling to catch-all error

2025-12-02T18:17:43Z

Since EXTEND is not used anymore, it's fine to handle it in our catch-all branch for unrecognized/unsupported cells.

proto: Explain why we have the backward sink readiness check

2025-12-02T18:16:26Z

proto: Resolve some clippy warnings, remove allows

2025-11-24T17:03:48Z

proto: Reword a nonsensical TODO

2025-11-24T17:03:48Z

This TODO was copied over from the client reactor, but it doesn't make any sense here (we don't yet handle control messages in the backward reactor).