mirrors/arti.git/crates/tor-rtmock/src, branch arti-v1.2.7mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.72024-08-28T14:27:46Zextract 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:06cbee5e7679cd11b4568b7538d39231f45378dbtor-rtmock docs: We have CoarseTimeProvider now2024-07-30T17:42:41ZIan Jacksonijackson@chiark.greenend.org.uk2024-07-25T13:59:11Zurn:sha1:0770be9de6081ea5ae3ed1ba7cff56ecbd466ea9
Improve/replace some out-of-date notes in the docs.
tls: Support export keying material (RFC 5705)2024-06-18T14:18:58ZDavid Gouletdgoulet@torproject.org2024-06-04T18:56:21Zurn:sha1:144522a38a511ee0dd1f5bcee9bec01c971d1f6b
Add a function to get the keying material as detailed by RFC 5705.
Because native-tls doesn't have such support, there is a place holder
panic!() for now.
This means that for the forseable future, relay would only work with
rustls until we figure out a solution for native-tls.
Closes #1432
Signed-off-by: David Goulet <dgoulet@torproject.org>
Change deftly syntax to post 0.12.1 version2024-06-17T18:13:06ZIan Jacksonijackson@chiark.greenend.org.uk2024-06-17T17:33:09Zurn:sha1:dddf07561868579ea687eeadaa8f863aa833c764
* Change `pub` to `export`
* Change the `=` in define to `:`
* Change `pub_template_semver_check` to `template_export_semver_check`
Right now, 0.12.1 supports both syntaxes. I have verified this branch
also compiles with
https://gitlab.torproject.org/Diziet/rust-derive-deftly/-/merge_requests/402
ee171ffaf56d7dcb7d75584054921153fe19b222
Re-run maint/add_warning.2024-05-06T13:31:35ZNick Mathewsonnickm@torproject.org2024-05-06T13:23:41Zurn:sha1:97f452ec9958bf7d8ca3275c39655814a4494637
This commit is automatically generated.
Suppress a spurious dead code lint2024-04-25T14:22:32ZIan Jacksonijackson@chiark.greenend.org.uk2024-04-24T10:51:38Zurn:sha1:27475324480a9a878db578dee5ec7a83db874ef2tor-rtmock: Remove a todo comment2024-04-03T12:15:08ZIan Jacksonijackson@chiark.greenend.org.uk2024-04-02T14:36:30Zurn:sha1:482de7997a32efe317498a13712da2544c481b06
derive-deftly 0.10.x rejects unrecognised `#[deftly]` attributes.