mirrors/arti.git/crates/tor-circmgr, 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-09-03T17:57:12ZBump all the unstable tor- and arti- crates to 0.22.0.2024-09-03T17:57:12ZGabriela Moldovangabi@torproject.org2024-09-03T17:25:54Zurn:sha1:c3c266707f2fd361a447d922c5acfbb3938d88f2
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.22.0
done
```
oneshot-fused-workaround: Set the initial version to 0.1.0.2024-09-03T15:22:43ZGabriela Moldovangabi@torproject.org2024-09-03T14:55:25Zurn:sha1:a88af5e93762a8cd95321a3adc31b2bc2ae3bd4d
This is the first time we're publishing this, so let's start at 0.1.0.
Fix formatting issues introduced by fixup-features.2024-09-03T10:00:30ZGabriela Moldovangabi@torproject.org2024-09-03T09:21:55Zurn:sha1:dfe02110114be3f17e439bf99f776521fd044e15Run fixup-features in preparation for release.2024-09-03T10:00:30ZGabriela Moldovangabi@torproject.org2024-09-03T09:10:10Zurn:sha1:1eea611d14630c2901962e5cba408f2b7cf456fcFix typos2024-09-03T08:09:02ZDimitris Apostoloudimitris.apostolou@icloud.com2024-09-03T08:09:02Zurn:sha1:676f913463b7d84f34dd6101b99d03ef79cf57adextract 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.
tor-circmgr: removed unused 'skip_guard_subnet_check' workaround in tests2024-08-15T17:54:58ZSteven Englersmengler3@gmail.com2024-08-15T15:35:49Zurn:sha1:4af7ab716019c85a0373fd82ee22daab3c74a0cetor-circmgr: removed unused "chosen exit" functionality2024-08-15T17:54:58ZSteven Englersmengler3@gmail.com2024-08-15T15:32:46Zurn:sha1:e03a2b6cc1f9ee07404c6ac0cd736fc4eba86a99tor-circmgr: fix flaky `path::exitpath::test::by_ports` test2024-08-13T18:44:24ZSteven Englersmengler3@gmail.com2024-08-13T18:10:10Zurn:sha1:e0b7f6582283e8cdb721b2df23e99257e4191eb0
The `path::exitpath::test::by_ports` test sometimes failed now that the
test is using a `GuardMgr` since `select_guard`, when given a chosen
exit, only ensures that the guard and chosen exit are not in the same
family. It does not ensure that the guard and exit do not share an
extended family. This commit relaxes an assertion in the test.
```text
thread 'path::exitpath::test::by_ports' panicked at crates/tor-circmgr/src/path/exitpath.rs:295:9:
assertion failed: r1.can_share_circuit(r3, subnet_config)
```
This "chosen exit" functionality isn't actually being used anywhere
(`ExitPathBuilderInner::ChosenExit` is only ever constructed in tests).
tor-circmgr: assert in test that exit path begins with guard2024-08-13T01:13:17ZSteven Englersmengler3@gmail.com2024-08-13T01:12:32Zurn:sha1:2a4208aa0675c966c58fbb368745254545e6e923