mirrors/arti.git/crates/tor-proto/src/channel, branch arti-v2.5.1

tor-proto: extend circ handshake tests to close the circuit

2026-07-30T17:46:47Z

tor-proto: rename some methods on test `ConnInspector`

2026-07-30T17:46:47Z

tor-proto: don't drop stream rx in tests

2026-07-30T17:46:47Z

Otherwise the new circuit gets closed immediately by the relay.

tor-proto: add 'test_utils' mod for channel tests

2026-07-30T03:41:41Z

These help to establish connected channel objects to be used for tests.

proto: Use PeerInfo to log responder channel addr

2026-07-29T13:30:29Z

Inbound channel (as responder) don't have a ChannelMethod as they are not initiating the type of transport to use (PT vs Direct). It would result in a log line when receiving a channel request: DEBUG tor_proto::channel::handshake: Completed handshake without authentication to [? ] stream_id=Chan 2 This commit uses the `PeerInfo` which is wrapped in a `MaybeSensitive` and thus safe to log. Signed-off-by: David Goulet

align DestroyReason with torspec!490

2026-07-28T09:33:30Z

tor-checkable: Rename `TimeBound::is_valid_at` to `check_valid_at`

2026-07-23T10:13:34Z

I find this names confusing. To my mind "is" implies a function returning `bool`.

tor-checkable: TimeBound: Make wrapped type an associated type

2026-07-23T10:13:34Z

It wouldn't make much sense for one concrete type to be unwrappable variously as different inner types.

tor-checkable: TimeBound: remove Error associated type

2026-07-23T10:13:34Z

This was always TimeValidityError. And we want to rely on that so we can do the validity checking more centrally.

proto: Return the incoming streams from the create handler

2026-07-22T12:12:10Z

We need to return the "futures::Stream of Tor streams" from the CREATE handler, because these need to be handled from `arti-relay`, as per `doc/dev/notes/relay-streams.md` This commit is intentionally (slightly) misformatted to make reviewing a bit easier (the next commit will rustfmt everything). Part of #2612