mirrors/arti.git/crates/tor-rtmock, branch arti-v1.1.10mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.102023-10-31T13:12:35ZPatch version bumps in crates without breaking changes2023-10-31T13:12:35ZNick Mathewsonnickm@torproject.org2023-10-31T13:00:42Zurn:sha1:537d98a12eedf5604fe28183ec603dd3609bb070
```
These crates have new APIs:
tor-async-utils ADDED
tor-config ADDED
tor-hscrypto ADDED
tor-netdoc ADDED, plus BREAKING-experimental.
These crates have patch-level changes only:
tor-netdir (bugfix only). (re-exposes netdoc)
arti-rpcserver (tweaks only, uses nothing that broke.)
arti 1.1.10, no stable public APIs.
```
Minor version bumps in crates with breaking changes.2023-10-31T13:12:35ZNick Mathewsonnickm@torproject.org2023-10-31T12:54:00Zurn:sha1:4460d8b3a5f801db2b20ca0e83dadd0bc8ccf5da
```
tor-basic-utils BREAKING
tor-rtmock BREAKING.
tor-cert BREAKING
tor-cell BREAKING
tor-proto BREAKING: re-exposes cell. (Also BREAKING-experimental)
tor-chanmgr BREAKING: Re-exposes proto.
tor-ptmgr BREAKING: re-exposes tor-chanmgr
tor-guardmgr BREAKING: re-exposes proto. (Only for ClockSkew I think?)
tor-circmgr BREAKING: re-exposes proto
tor-dirclient BREAKING
tor-hsclient BREAKING, re-exposes proto.
tor-hsservice BREAKING, re-exposes proto.
tor-hsrproxy BREAKING
arti-client BREAKING: re-exposes proto.
arti-hyper: BREAKING, re-exposes arti-client.
tor-dirmgr Let's assume BREAKING, very high-level.
tor-keymgr BREAKING, but experimental.
```
Run "fixup-features" in preparation for release this week.2023-10-29T12:25:28ZNick Mathewsonnickm@torproject.org2023-10-29T12:25:28Zurn:sha1:d804f1a2bc43545db5d2cce379dbc1bad7728176tor-rtmock: MockRuntime::test_with_various: Print what we're doing2023-10-16T12:38:30ZIan Jacksonijackson@chiark.greenend.org.uk2023-10-12T13:28:37Zurn:sha1:6345e398fb81e93b5f1f6618a8c83f5821f610af
Without this, it can be a bit confusing since you just get the
output (if any) of all the test runs, concatenated. It seems sensible
to put the framing centrally.
And, this would be helpful if the test fails for any reason.
tor-rtmock: MockExecutor: Provide n_tasks accessor2023-10-16T12:38:30ZIan Jacksonijackson@chiark.greenend.org.uk2023-10-10T15:07:39Zurn:sha1:b3d36a945f3090a370affdce3ff67f0cf4920b62oneshot: Apply deferred rustfmt churn2023-10-11T15:19:46ZIan Jacksonijackson@chiark.greenend.org.uk2023-10-11T15:09:09Zurn:sha1:665ba4f6b6ed2de6f723177d5472e7ee1440599e
cargo fmt, precisely.
oneshot: Use veneer in tor-rtmock2023-10-11T15:19:21ZIan Jacksonijackson@chiark.greenend.org.uk2023-10-11T14:01:34Zurn:sha1:87729eca8912a64cc0ad1af1f7bf75a39c87dabetor-rtmock: simple_time: Don't export State2023-10-05T18:09:19ZIan Jacksonijackson@chiark.greenend.org.uk2023-10-05T18:07:24Zurn:sha1:26684c5f4e1ad40cdddd3ee0b771ae47c44f1812
This was a slip.
tor-rtmock: Provide a comprehensive example2023-10-05T18:09:17ZIan Jacksonijackson@chiark.greenend.org.uk2023-10-05T15:14:15Zurn:sha1:5b5380db69a8f73cd247790f3967ea6d31f69d29tor-rtmock: Update the rubric for current recommendations2023-10-05T18:08:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-10-05T18:06:11Zurn:sha1:5f34f9bc9220d53d364eebd093c8f912ab682ccc