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

proto: Add an immediate order for client CircuitEvent ordering

2025-12-10T16:04:26Z

With a protocol violation, we have to immediately deal with such event before emitting anything on the wire. Signed-off-by: David Goulet

proto: Rename CircuitAction and cie to CircuitEvent

2025-12-10T16:04:26Z

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

proto: #[macro_use] be gone!

2025-12-10T16:04:26Z

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

2025-12-10T16:04:26Z

Signed-off-by: David Goulet

proto: Add TODO in client reactor for bad cell

2025-12-10T16:04:26Z

Because of https://gitlab.torproject.org/tpo/core/torspec/-/issues/385 Signed-off-by: David Goulet

proto: Move relay specific unit test to relay module

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: Make ClientCircChanMsg pub(super)

2025-12-10T16:03:12Z

Signed-off-by: David Goulet

proto: Move unit tests and minor fix

2025-12-10T16:03:12Z

Move the client specific unit tests into the client module. 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