mirrors/arti.git/crates/tor-circmgr, branch arti-v1.0.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.0.02022-09-01T12:59:49ZBump crate versions in preparation for Arti 1.0.0 release.2022-09-01T12:59:49ZNick Mathewsonnickm@torproject.org2022-09-01T12:52:51Zurn:sha1:96875ea20875e3a5cfc9f348365f19a158578190
Because we want to work more on ensuring that our semver stability
story is solid, we are _not_ bumping arti-client to 1.0.0 right now.
Here are the bumps we _are_ doing. Crates with "minor" bumps have
had API breaks; crates with "patch" bumps have had new APIs added.
Note that `tor-congestion` is not bumped here: it's a new crate, and
hasn't been published before.
```
tor-basic-utils minor
fs-mistrust minor
tor-config minor
tor-rtcompat minor
tor-rtmock minor
tor-llcrypto patch
tor-bytes patch
tor-linkspec minor
tor-cell minor
tor-proto minor
tor-netdoc patch
tor-netdir minor
tor-persist patch
tor-chanmgr minor
tor-guardmgr minor
tor-circmgr minor
tor-dirmgr minor
arti-client minor
arti-hyper minor
arti major
arti-bench minor
arti-testing minor
```
Shorten the duration needed in preemptive::test::does_not_predict_old_ports.2022-08-31T12:52:40ZAlexander Færøyahf@torproject.org2022-08-31T11:54:12Zurn:sha1:3e3a68683c96fd79e775e9dd707138398ca32b8c
This patch shortens the duration of the `does_not_predict_old_ports`
test in the preemptive module. AppVeyor spawns its VMs/containers per
build, so the `Instant::now()` call returns a value smaller than `60 *
60 + 1` which causes the subtraction to overflow and thus panic.
Thanks to @trinity-1686a for the help here.
See: tpo/core/arti#563.
circmgr: treat usage as sensitive.2022-08-25T15:02:06ZNick Mathewsonnickm@torproject.org2022-08-25T15:02:06Zurn:sha1:051022482086aacf29fe458c6eb5d3fb63348604enable doc_auto_cfg feature on every crate when documenting for docs.rs2022-08-24T16:22:41Ztrinity-1686atrinity@deuxfleurs.fr2022-08-17T19:13:13Zurn:sha1:7f939fa4804b3c934343141b79e8e2ded5fe0b0dMerge branch 'channel' into 'main'2022-08-17T10:26:25ZIan Jacksoniwj@torproject.org2022-08-17T10:26:25Zurn:sha1:46d9dadd02c95150296e096a39f45e648363bbd5
Channel padding
See merge request tpo/core/arti!657channel usage: Rename CU::UserTraffic from CU::Exit2022-08-17T09:54:41ZIan Jacksonijackson@chiark.greenend.org.uk2022-08-11T10:39:39Zurn:sha1:3aed28acd42dbf5342932e2f6f42cc2ddbbe8c50
As suggested in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/657#note_2827246
Add semver notes2022-08-17T09:54:41ZIan Jacksonijackson@chiark.greenend.org.uk2022-08-09T12:06:49Zurn:sha1:d9338293c8d6702087d38c1442965f60c6c7ce9cMove ChannelUsage from tor_proto to tor_chanmgr2022-08-17T09:54:41ZIan Jacksonijackson@chiark.greenend.org.uk2022-08-08T15:33:33Zurn:sha1:5db974ef72eb1250ab27cd7e21141f64d8778776
Replace Channel::note_usage with Channel::engage_padding_activities,
which unconditionally causes the channel to (start to) do netflow
padding things.
The condition now lives in chanmgr.
Addresses
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/657#note_2826094
chanmgr: Use NetDirProvider::params and Arc<dyn..Netparameters>2022-08-17T09:54:41ZIan Jacksonijackson@chiark.greenend.org.uk2022-08-08T12:47:02Zurn:sha1:48fc5d3c39ccb8de3d3b52f34c5c76cae6806714
This gets rid of many Result(). Many parameters are renamed.
Test cases of the now-impossible branch are removed.
Deleting the match from padding_parameters will come in a moment.
I've split off that commit since it has much whitespace noise.
for now, change the error type to Void.
Additionally, mark the LostUsablityRace error as a "reset".2022-08-16T18:03:43ZNick Mathewsonnickm@torproject.org2022-08-16T15:23:02Zurn:sha1:8862eb1e3493bd0be53ee8a7678ddc8529f22309