mirrors/arti.git/crates/tor-hsservice/src, 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-28T10:54:48Zproto: Add a circuit module shared between client and relay impls.2025-08-28T10:54:48ZGabriela Moldovangabi@torproject.org2025-08-26T17:48:56Zurn:sha1:4ee5a4abcee895e79588888f6bc8eaa6963a6ba7
This is just code motion (I suggest reviewing with `--color-moved`).
This also moves the implementation-agnostic parts from
`tor_proto::client::circuit` to a new `tor_proto::circuit` module.
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:2de5c18fae7be30c4ab3c3fae520c81fb3ff74edMerge branch 'relay-reactor-placeholder' into 'main'2025-08-18T19:08:47ZDavid Gouletdgoulet@torproject.org2025-08-18T19:08:47Zurn:sha1:a3bf2347bf0d91d08b2551bd0f3652ee8ae34744
proto: Add a placeholder for the relay reactor.
See merge request tpo/core/arti!3162Merge branch 'fix-nightly-warn' into 'main'2025-08-18T17:00:41ZNick Mathewsonnickm@torproject.org2025-08-18T17:00:41Zurn:sha1:594ba18674a74ca8d0bbf78a25f73bde079a3c29
Fix clippy errors on nightly
See merge request tpo/core/arti!3148proto: 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.
tor-hsservice: Move check for enable_pow without hs-pow-full feature.2025-08-14T22:23:29ZWesley Aptekar-Casselsme@wesleyac.com2025-08-13T18:37:00Zurn:sha1:89173f3cf319f248bb1bffed1476b0ff3da72000
This also make this check a error rather than a warning.
tor-hsservice: Add note about check_solve implementation.2025-08-13T18:43:05ZWesley Aptekar-Casselsme@wesleyac.com2025-08-13T18:34:59Zurn:sha1:0a98ff1e9328d5ba5feb461be1d0451f40ccc220tor-hsservice: Fix error message.2025-08-13T18:43:05ZWesley Aptekar-Casselsme@wesleyac.com2025-08-13T18:23:01Zurn:sha1:3c4749b2c47792c284efa961f8898fe20f71a3c6tor-hsservice: Change capping of PoW effort.2025-08-13T18:43:05ZWesley Aptekar-Casselsme@wesleyac.com2025-08-13T18:20:11Zurn:sha1:8e9e5a2f6ff20360816896b971408e8bf1b5c7ea
This caps the PoW effort during sorting, rather than at intake.
This allows us to record efforts that are capped in our metrics
histogram while only recording metrics after the PoW solve has actually
been verified.