mirrors/arti.git/crates/arti-testing/src/rt, branch arti-v1.4.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.02025-01-15T13:49:17Ztor-rtcompat: Rename UnsupportedStreamOps to NoOpStreamOpsHandle (fmt).2025-01-15T13:49:17ZGabriela Moldovangabi@torproject.org2025-01-13T11:49:37Zurn:sha1:dc4fe47d5388074352ac00b561bed978779446e0tor-rtcompat: Rename UnsupportedStreamOps to NoOpStreamOpsHandle.2025-01-15T13:49:17ZGabriela Moldovangabi@torproject.org2025-01-13T11:48:16Zurn:sha1:4ec53ca4dea324c2c170885d8556a67c802e491d
This renames UnsupportedStreamOpsHandle to NoOpStreamOpsHandle for
clarity (the old name kind of sounded like the name of an error type).
tor-rtcompat: Implement new_handle() using TcpSockFd (fmt).2025-01-15T13:49:17ZGabriela Moldovangabi@torproject.org2025-01-09T19:08:27Zurn:sha1:1896261523f14beb8eb7ee1bf1ba5f129c749dcator-rtcompat: Implement new_handle() using TcpSockFd.2025-01-15T13:49:17ZGabriela Moldovangabi@torproject.org2025-01-08T19:35:08Zurn:sha1:f70ef5e04483c2d41f2efd98c9854e6447654bc6tor-rtcompat: Add the ability to get a StreamOps handle.2025-01-15T13:49:17ZGabriela Moldovangabi@torproject.org2025-01-08T11:06:59Zurn:sha1:267235969df65d975b5deb01c342e1073d4c3847
Needed for cases where we wrap an object that implements `StreamOps` in
an external type, thereby losing access to the `StreamOps`
functionality. For example, during the channel handshake, we `.split()`
the stream that implements `StreamOps`, which leaves us with a
`SplitSink` and a `SplitStream`, neither of which implement `StreamOps`.
Getting a handle to the underlying object that implements `StreamOps`
(for example, a file handle) *before* the stream is `.split()` enables
us to use `StreamOps` to manipulate the underlying split stream.
This commit also introduces a special `UnsupportedStreamOpsHandle`,
which is a type that implements `StreamOps`, but always returns an
error. This type is meant to simplify error handling and usage, and is
meant to be used in cases where `StreamOps` is not supported. TODO: the
name of this type is pretty confusing (it's very similar to
`UnsupportedStreamOp`, which is an error type), and should probably be
renamed to something else (`NoOpStreamOpsHandle`,
`BrokenStreamOpsHandle`, `DummyStreamOpsHandle` come to mind...).
Note: this changes the `StreamOps` trait to be slightly different from
what I originally envisioned in !2660 and #1769
tor-rtcompat: Implement StreamOps for all the stream types.2024-12-10T10:34:48ZGabriela Moldovangabi@torproject.org2024-12-05T15:00:11Zurn:sha1:56e9b79b09c65caee25a50c083fdd40f8c66f040
Part of #1769
rtcompat: remove async_trait from NetStreamListener.2024-09-24T13:10:11ZNick Mathewsonnickm@torproject.org2024-09-22T19:26:30Zurn:sha1:b53b465d81b39433048b459924e0c481bad84a07
(The trait no longer has any async methods.)
Make Runtime require NetStreamProvider<unix::SocketAddr>2024-09-24T13:10:11ZNick Mathewsonnickm@torproject.org2024-09-22T19:17:14Zurn:sha1:7a56ae00ffb6e45783b0eb837098ea894ade5861Documentation updates for "NetStreamProvider" rename2024-09-24T13:10:11ZNick Mathewsonnickm@torproject.org2024-09-19T12:13:29Zurn:sha1:07ca20d4aaa7081bd901cc487fbb093bf05f5a76
Stop referring to TCP streams in its documentation;
update other documentation to refer to NetStreamProvider
rather than TcpProvider.
rtcompat: Rename TcpProvider to NetStreamProvider.2024-09-24T13:10:11ZNick Mathewsonnickm@torproject.org2024-09-19T11:55:22Zurn:sha1:8c2d84000e4d5ba74e7b6b4e9dac3fc700f618b5
(And similarly rename TcpListener to NetStreamListener,
along with their TcpStream/TcpListener associated types.)
These types are about to become generic over addresses,
and therefore shouldn't be named after TCP.
Renaming was done mostly with Rust Analyzer,
except for some macros that needed to be hand-edited.
(I'll revise the comments in the next commit;
this one is all about renaming.)