mirrors/arti.git/crates/tor-proto/src/stream, branch arti-v2.0.0

Apply 1 suggestion(s) to 1 file(s)

2026-01-27T16:22:08Z

Co-authored-by: carti-it

tor-proto: Report CircuitClosed on unexpected stream rx close

2026-01-22T17:14:14Z

As near as I can tell, there are only three ways that the sender corresponding to this rx can be dropped: - `StreamMap::terminate` because the stream object itself was dropped. (But see #2323.) - `StreamMap::close_stream` because an END message or similar has been received. (But see #2322.) - The `StreamMap` has been dropped. The first two cases are already handled, and AFAICT the third can only happen when the circuit hop closes. That makes `CircuitClosed` the appropriate error here, not `StreamProto`. Part of a fix for #2304.

proto: Fix docs post-refactoring

2026-01-13T17:54:18Z

proto: Dedupe IncomingStreamRequestHandler

2026-01-12T19:10:54Z

proto: Fix a number of newly broken doc links

2025-11-24T17:03:48Z

proto: Adjust docs to refer to the new location of StreamReceiver

2025-11-24T17:03:48Z

While we still re-export StreamReceiver from the client module, I want to avoid importing it from there in the implementation-agnostic modules, just to make it clearer we're not using client-specific types.

proto: Move StreamComponents to top-level stream mod

2025-11-24T16:47:11Z

proto: Move raw under top-level stream mod

2025-11-24T16:47:11Z

proto: Move StreamTarget to stream module

2025-11-24T16:47:11Z

proto: Move StreamReqInfo to stream module

2025-11-24T16:31:55Z