mirrors/arti.git/crates/tor-rtmock/src, 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: Expose FakeStream and friends; fix compilation in tor-rtmock2024-09-24T13:10:11ZNick Mathewsonnickm@torproject.org2024-09-23T17:20:47Zurn:sha1:014ea0c7512d2199d8b5b98c75e38fba4938afda
It turns out that these types are generally useful, and that they
are in fact needed for tor-rtmock to compile without a PreferredRuntime.
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.
extract tor_async_utils::oneshot into ::oneshot-fused-workaround2024-08-28T14:27:46ZJim Newsomejnewsome@torproject.org2024-08-22T19:20:36Zurn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1
Having this in the `tor-async-utils` crate prevents us from doing both
of the following without introducing a circular dependency:
* using it in `tor-rtmock` (which we currently do, particularly in
tests).
* using `tor-rtmock` to test things in `tor-async-utils`. We don't do
this yet, but it is generally sensible to do so. In particular we
want to move the `stream_peak` module there, which is currently tested
with `tor-rtmock`.
Moving this into its own crate avoids this circular dependency.
Match previous backtrace formatting2024-08-08T15:44:17ZRobin Leander Schröder1473-rls@gitlab.torproject.org2024-08-07T17:09:26Zurn:sha1:62254c50189bda8772762e77239077d6886b279a
std::backtrace::Backtrace's Display looks the same as
backtrace_rs::Backtrace's Debug
Use std::backtrace instead of backtrace crate2024-08-01T12:18:40ZRobin Leander Schröder1473-rls@gitlab.torproject.org2024-08-01T12:07:36Zurn:sha1:9f31e6b650f004ccf88446e8b2a39f1381995c09
Removes resolve_backtraces from rtmock since it is no longer needed as
stdlib's backtraces automatically lazily resolve without needing a &mut.
tor-rtmock docs: Add some more discussion of the simulated time2024-07-30T17:42:44ZIan Jacksonijackson@chiark.greenend.org.uk2024-07-25T13:51:03Zurn:sha1:06cbee5e7679cd11b4568b7538d39231f45378db