mirrors/arti.git/crates/arti-client/src/lib.rs, branch arti-v1.5.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.02025-08-18T16:09:04Zproto: Move the `stream` module under `client` (breaking).2025-08-18T16:09:04ZGabriela Moldovangabi@torproject.org2025-08-18T15:52:38Zurn:sha1:702e7276898d3f31e22033c5b64fea91703f3701
The `stream` module is client-specific, for the most part, so I am
moving it under `client`. Later on, we will factor out the parts that
can be shared with the relay implementation.
Note: this is a breaking change as the deleted `stream` module was
`pub`. We could've kept the module and reexported from it the public
types from `tor_proto::client::stream`, but I think it's better to have
this `client` namespacing, because it makes the separation between the
client and relay parts clearer.
Switch Cargo.toml files to edition 2024.2025-08-07T15:28:36ZNick Mathewsonnickm@torproject.org2025-08-06T01:19:58Zurn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
arti-client: Fix test for FlowCtrl=2.2025-08-06T15:52:20ZNick Mathewsonnickm@torproject.org2025-08-06T15:52:20Zurn:sha1:1af42e52578bd1b6fc5b59cdc389d6be2f68f5e1
(It is possible for arti-client to have flowctl-cc disabled, but for
tor-proto to have it enabled.)
tor_proto: add FLOWCTRL_CC to supported_client_protocols2025-08-06T12:27:58ZNick Mathewsonnickm@torproject.org2025-08-06T12:27:58Zurn:sha1:5b0580386bb26d3198e9a77d1da6680701680fab
Since we now allow it to be turned on, we can include it among our
supported protocols.
Temporarily suppress mismatched_lifetime_syntaxes.2025-07-07T15:50:04ZGabriela Moldovangabi@torproject.org2025-07-07T15:50:04Zurn:sha1:a11b611466a5a73f5e06a0aabd17284a57d12fe3
See #2060.
protover, *: Add documentation about what "supported" means.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-14T00:42:31Zurn:sha1:11148719ba04aab37c7784d198018eeacced69c2arti-client: Keep a somewhat accurate notion of our release date.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-07T16:05:33Zurn:sha1:ad54680765772ccb473abde8ca0524d81f384b21
This doesn't need to be perfect, but we need to use it to see
if a consensus is new enough that we should obey its
recommendations.
This commit also adds a script to update or check our release date,
and calls this script from our cargo-publish script.
Add warnings about removing supported protocols.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-07T15:27:42Zurn:sha1:ba612260ae603c8e5eba37206c21fd089afe075darti-client: Implement the basics of protocol enforcement.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-07T15:04:08Zurn:sha1:e4348e5d44da5d0dc2aaac0968dd5392500fbb46
This is the major part of #1849.
New functions to report supported subprotocols2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-02T18:00:00Zurn:sha1:efe36d15de88ec5b7f39db99f9d2a58e4e5db7ac
Part of #1849.
Note that these functions are distributed across crates,
so that if (in the future) we stop doing API breaks
with every release, we will get the right outputs.
Note also that these functions build the list of protocols
out of specific symbolic features, rather than numbers:
this makes it easier to avoid errors about "which feature was
Relay=4 again", and easier to avoid accidentally referring to a
protocol that doesn't exist, like "Consensus" (should be "Cons")
or "HsDir" (case is wrong).