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

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: 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: 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 ClientCircChanMsg into client module

2025-12-10T16:03:11Z

Next commit will also move the Relay specific set into the relay module. These two sets are becoming specific to the reactor as the circuit reactor communication channel will use AnyChanMsg instead. Signed-off-by: David Goulet

Merge branch 'relay-streams2' into 'main'

2025-12-02T20:08:50Z

proto: Start handling incoming streams in the relay reactor See merge request tpo/core/arti!3487

proto: Allow unstable_name_collisions in several places

2025-12-01T10:53:23Z

proto: Appropriately gate STREAM_READER_BUFFER to satisfy clippy

2025-11-24T17:03:48Z

proto: Deduplicate msg_streamid()

2025-11-24T17:03:48Z

Initially I wanted to turn `msg_streamid()` into a method on `UnparsedRelayMsg`, but I ultimately decided against it, because it feels like it doesn't belong there (even though intuitively, I would've expected it to handle the mismatch between stream ID and cell command internally). This is because all the `UnparsedRelayMsg` methods return `tor_bytes::Result`, and do not actually do any validation beyond some length checks on the various fields.

proto: Move a couple of stream-related constants to stream mod

2025-11-24T17:03:48Z