mirrors/arti.git/crates/arti-testing/src, branch arti-v1.4.1mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.12025-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
clippy: deny `mod_module_files`2025-01-06T23:09:41ZSteven Engleropara@torproject.org2025-01-06T23:02:49Zurn:sha1:252a3a803b2db65792db5bd51dee8950d8557e0d
Denies 'mod.rs' files for consistency.
https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files
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
add_warnings, *: Allow clippy::needless_lifetimes2024-12-03T14:27:26ZNick Mathewsonnickm@torproject.org2024-12-03T14:15:50Zurn:sha1:64cc3f2ed3eea0b7c5cc89ae07cbdadfdc1646fb
In 1.83, this warning triggers on many of our crates.
We're thinking of fixing them all, but for now,
we're going to disable the warning.
This is part of #1765.
TimerangeBound: Stop using std::ops::Bound.2024-11-25T18:20:11ZWesley Aptekar-Casselsme@wesleyac.com2024-10-15T13:58:29Zurn:sha1:1659495eb30ae6a17058418b6d00592373cfdf65
Fixes: #1691
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.)