mirrors/arti.git/crates/arti-testing/src/rt/badtcp.rs, branch arti-v1.3.2mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.22024-12-10T10:34:48Ztor-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.)
rtcompat: Remove accept() from TcpListener2024-09-24T13:10:11ZNick Mathewsonnickm@torproject.org2024-09-18T22:57:09Zurn:sha1:168f55df05f4b56fd61423c020ce62e93f1d7a9f
It's redundant with the incoming() method (which turns the
TcpListener into a Stream of connections), and nothing actually used
it outside of tests.
Removing this method allows us to simplify our TcpListener code a
good deal, as can be seen by some of the implementations we removed
from our example and testing code.
rng ranges: Use gen_range_infallible() for Duration::ZERO..=T2023-07-10T15:08:03ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-07T13:19:55Zurn:sha1:b151237a7f8651ed8694748832af05786a7eccfdrng ranges: Use inclusive Duration ranges in several places2023-07-07T15:13:52ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-07T13:10:23Zurn:sha1:bcc3e6fef8b863fa6a863aae2d6234fba7fb99f6
Many of these call sites would panic if, somehow, the upper bound was
zero. In most cases it is very complicated to see if whether this
could happen.
However, there is a better answer:
Durations are (conceptually) dense, so picking the closed set (which
includes its boundary) rather than the open one (which doesn't) will
make little practical difference.
So change four call sites to use `..=` instead of just `..`.
arti-testing: Make Action implement Copy2022-03-10T13:45:56ZNick Mathewsonnickm@torproject.org2022-03-10T13:45:56Zurn:sha1:d1b151436ead6515aacc238a896b0f92700a31cdarti-testing: reverse two more attrs in attempt to fix min-versions2022-03-07T20:29:44ZNick Mathewsonnickm@torproject.org2022-03-07T19:34:02Zurn:sha1:a460de6e75c3cd613d6b7e1cee3adfb269ff3757