mirrors/arti.git/crates/tor-hsservice/src/publish/reactor.rs, branch arti-v1.9.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.9.02025-11-24T16:28:07Zopentelemetry: Instrument a bunch of functions.2025-11-24T16:28:07ZWesley Aptekar-Casselsme@wesleyac.com2025-11-24T16:28:07Zurn:sha1:a4db6a7495b13dd7b00416dd1660a5ad82b60919
These are all aimed at figuring out in more detail what's going on
in #2079 and related issues.
Fix name of clippy lint to unchecked_time_subtraction (2)2025-11-06T11:28:22ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-06T11:23:25Zurn:sha1:a5fd5c48ea059a80cc1f6c50e248654b5ff3aaff
Run maint/add_warning
hsservice: Move derive_more::From out of internal_prelude.2025-08-19T13:46:54ZNick Mathewsonnickm@torproject.org2025-08-19T13:46:54Zurn:sha1:6cb98ccc344768c0cff6b7136ea81c38d2f4e990
This fixes an error from nightly. The trouble is that with nightly,
there's a now a [derive macro for From][issue]. That doesn't cause
a conflict when we `use derive_more::From`, but it _does_
cause a conflict when we import `derive_more::From` via
`use internal_prelude::*`.
So as a solution, we just import `derive_more::From` explicitly.
Closes #2124
[issue]: https://github.com/rust-lang/rust/pull/144922
misc: cleanup now that `_report!` macros support fields2025-08-18T19:45:55ZSteven Engleropara@torproject.org2025-08-09T20:31:11Zurn:sha1:2de5c18fae7be30c4ab3c3fae520c81fb3ff74edproto: 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.
hs: Use the new Tunnel interface for onion service2025-08-05T18:23:02ZDavid Gouletdgoulet@torproject.org2025-05-07T18:10:53Zurn:sha1:8333a2d7c9e4842753e65d978087e54a8ad43789netdoc, hsservice: Respect maximum descriptor sizes2025-07-10T13:41:48ZNick Mathewsonnickm@torproject.org2025-06-24T15:44:57Zurn:sha1:1df1014e9d52ae1c848f97daadfac4d7e1c61d36
It would be better to take a more sophisticated approach;
see #2048.
hs*: Define some HsDesc errors as _suspicious_.2025-07-10T13:41:48ZNick Mathewsonnickm@torproject.org2025-06-23T18:35:38Zurn:sha1:6ff683b2cf209ff0598efcdae7947ed6a8fbebbe
These errors are suspicious as hsdir inflation attacks, in the
context of prop360.
hs*: Include SourceInfo when making HsDesc requests.2025-07-10T13:41:48ZNick Mathewsonnickm@torproject.org2025-06-18T17:16:13Zurn:sha1:451fcbaac915b0662ffba7c3ff07f6c7ebde095e