mirrors/arti.git/crates/tor-proto, 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:676f913463b7d84f34dd6101b99d03ef79cf57adMove stream_peek into tor-async-utils2024-08-29T14:08:06ZJim Newsomejnewsome@torproject.org2024-08-21T19:23:49Zurn:sha1:2a11886271c41a0e2449c944b2f24db7f243d506extract 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_proto::channel`: update comment to point to `tor-chanmgr`2024-08-27T14:33:11ZJim Newsomejnewsome@torproject.org2024-08-27T14:33:11Zurn:sha1:adada9b92f278cdb0a4a1e1fbdef91d0ec9c4a4d`circuit` docs: delete comment about no flow-control etc2024-08-26T19:53:11ZJim Newsomejnewsome@torproject.org2024-08-26T19:44:43Zurn:sha1:508d67054c282e9aedda4e5d1e700b8b9e5f3da1
There is now (sendme-style) flow control, and some fairness
(via round robin scheduling of streams).
`circuit` docs: delete "one big mutex" limitation2024-08-26T19:36:01ZJim Newsomejnewsome@torproject.org2024-08-26T19:36:01Zurn:sha1:e5918dfdc4f155ab0c973860a9522faa41f2137a
There is a mutex for some of the "mutable state", but the reactor only
needs to lock it when adding a hop. It's not needed "to process a cell"
or when streams send. Probably not worth calling out here.