mirrors/arti.git/crates/arti-testing/src/rt/count.rs, branch arti-v1.2.8mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.82024-09-24T13:10:11Zrtcompat: 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.)
Documentation 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.
arti-testing: Initial implementation2022-03-03T18:05:30ZNick Mathewsonnickm@torproject.org2022-03-02T15:03:19Zurn:sha1:9329c7b878eadba0344802632b97f23524c9d8f3
This commit adds a new program to try to implement the ideas behind
experimentation in arti#329. In particular, it tries to implement
basic client "can I bootstrap and connect" functionality testing,
with a lot of instrumentation, and support for breaking things.
So far, the instrumentation is limited to counting TCP bytes and
connections, and counting events. Still, this is enough to measure
behavior on some of the incorrect-clock tests.
NOTE:
For now, you are _required_ to pass in an explicit configuration, in
hopes that this will lead you to override your storage directories
for doing specific experiments.