mirrors/arti.git/examples/hyper-examples/src/bin, branch arti-v2.4.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.4.02026-03-24T16:04:08ZFix typos2026-03-24T16:04:08ZTobias Stoeckmanntobias@stoeckmann.org2026-03-24T16:04:08Zurn:sha1:1fb2b8dd4aee7c943ce90d6631be473f2a296fe6
Typos found with codespell
arti(-client)/tor-hsservice: return None for disabled service2025-10-16T22:48:46ZhashcatHitman3924-hashcatHitman@gitlab.torproject.org2025-10-05T02:19:12Zurn:sha1:9ff73cad32a87d64fb18d193582b2337c093e391
There is no longer a hard error anywhere for trying to launch a service
which is disabled in the config. Instead, it always means returning
`Ok(None)`.
The axum and hyper examples were updated again as a consequence.
Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>
arti(-client): graceful service disable in arti only2025-10-16T22:48:45ZhashcatHitman3924-hashcatHitman@gitlab.torproject.org2025-09-19T01:31:52Zurn:sha1:4ad013a8d3efe36b95ae15ffab717c3f9a974d17
When a service is disabled in the config, `arti::onion_proxy::Proxy`
handles it gracefully, and
`arti_client::client::TorClient::launch_onion_service_with_hsid` and
`arti_client::client::TorClient::launch_onion_service` both hard error.
The axum and hyper examples were updated again as a consequence.
Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>
arti/arti-client: add graceful service disable2025-10-16T22:48:45ZhashcatHitman3924-hashcatHitman@gitlab.torproject.org2025-09-11T21:07:51Zurn:sha1:ea5607ad762af6cf72c56f09ef2971420ca7cae3
Hidden services disabled in the config are now handled more gracefully
by arti/arti-client, before the hard error occurs.
The axum and hyper examples were updated as a consequence.
Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>
proto: 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.
hyper-examples: Run rustfmt2025-08-11T12:05:05ZIan Jacksonijackson@chiark.greenend.org.uk2025-08-11T12:05:05Zurn:sha1:c0f1237b0825cae317291e64487182bfe1e5cdc3Merge branch 'main' into !29412025-08-11T11:57:22ZIan Jacksonijackson@chiark.greenend.org.uk2025-08-11T11:57:22Zurn:sha1:d13be7eea65fb009511ad4e6a6600b3d222ef443
Conflicts:
examples/hyper/hyper-http-client-example/Cargo.toml
examples/hyper/hyper-http-hs-example/Cargo.toml
In both cases, just the change of edition, which I have applied to
examples/hyper-examples/Cargo.toml
instead.
hyper-examples: Cargo fmt2025-08-04T04:37:36Znieldcontact@ndvibes.com2025-08-04T04:37:36Zurn:sha1:7f8ad0d84b348bc6053a659358ec2335cdb5a440hyper-examples: Use std::time::Duration2025-08-04T04:35:08Znieldcontact@ndvibes.com2025-08-04T04:35:08Zurn:sha1:fe06c5e3d82ef88918d569b27c6ed3c73537b9f9hyper-examples: Use random nickname for onion service2025-08-04T04:24:44Znieldcontact@ndvibes.com2025-08-04T04:22:26Zurn:sha1:eeb45bfeef167a88c60291bf58a9d888964239c7