mirrors/arti.git - mirror of https://gitlab.torproject.org/tpo/core/arti

	Commit message (Collapse)	Author	Age	Files	Lines
*	proto: Add crate-level exports for two extra stream types (fmt)	Gabriela Moldovan	2026-06-17	1	-13/+0
\|
*	Remove unnecessary `doc(cfg(...))` attributes	Neel Chauhan	2025-12-04	1	-2/+0
\| \| \| \| \| \| \| \| \|	Fixes part of #2193. (Edits from nickm: I selected the cases here that I could verify were correct from immediate context.) Edited-by: Nick Mathewson <[email protected]>
*	proto: Move raw under top-level stream mod	Gabriela Moldovan	2025-11-24	1	-6/+1
\|
*	proto: Move IncomingStream* types to shared module	Gabriela Moldovan	2025-11-24	1	-5/+5
\|
*	proto: Fix doc links post-refactoring	Gabriela Moldovan	2025-10-21	1	-1/+5
\|
*	proto: Move dumb pipes to top-lvl stream module	Gabriela Moldovan	2025-10-21	1	-1/+0
\|
*	proto: Rename data cmd checkers to {Inbound,Outbound}DataCmdChecker	Gabriela Moldovan	2025-10-16	1	-2/+2
\| \| \| \| \| \|	The previous "incoming" terminology was rather ambiguous. Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3348#note_3275337
*	proto: Move IncomingDataCmdChecker to top-level stream module.	Gabriela Moldovan	2025-10-16	1	-1/+1
\| \| \| \| \| \| \|	This will be used by relays too (for validating incoming messages on streams). This is just code motion, so it's best reviewed with `--color-moved`.
*	proto: Split out DataCmdChecker into multiple types.	Gabriela Moldovan	2025-10-16	1	-0/+3
\| \| \| \| \| \| \| \| \| \| \|	The incoming one will be used for the exit relay implementation too. Also, with this change, receiving `CONNECTED` on an incoming stream will result in a clearer error message. Previously, the check against receiving `CONNECTED` on an incoming stream was bundled with the double-CONNECTED check for client data streams, so in the incoming stream case, the error message was misleading ("Received CONNECTED twice on a stream.").
*	proto: Avoid crate-pub reexports of shared types from the client module.	Gabriela Moldovan	2025-10-16	1	-1/+0
\| \| \| \| \|	This makes it easier to see which parts are implementation-agnostic (i.e. do not import from crate::client).
*	proto: Move cmdchecker under top-level stream module.	Gabriela Moldovan	2025-10-16	1	-2/+1
\| \| \| \| \|	The CmdChecker will be used by relays too, so I am moving it to the shared `stream` module.
*	proto: Move flow_ctrl module under stream.	Gabriela Moldovan	2025-10-07	1	-1/+0
\| \| \| \|	This will be used by exits too, so I am moving it out of `client`.
*	tor-proto: remove a `pub(crate) use` from `client::stream`	Steven Engler	2025-09-10	1	-2/+0
\| \| \| \| \|	For internal types, I think it becomes too much of a mess to export everything through a single module.
*	tor-proto: reorganize some flow control modules	Steven Engler	2025-09-10	1	-3/+2
\| \| \| \|	This is all private (or pub(crate)) code.
*	proto: Move the `stream` module under `client` (breaking).	Gabriela Moldovan	2025-08-18	1	-0/+47
	The `stream` module is client-specific, for the most part, so I am moving it under `client`. Later on, we will factor out the parts that can be shared with the relay implementation. Note: this is a breaking change as the deleted `stream` module was `pub`. We could've kept the module and reexported from it the public types from `tor_proto::client::stream`, but I think it's better to have this `client` namespacing, because it makes the separation between the client and relay parts clearer.