mirrors/arti.git/crates/tor-circmgr/src/lib.rs, branch arti-v1.8.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.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.
circmgr: Implement expiration for long-lived tunnels.2025-11-12T15:00:55ZNick Mathewsonnickm@torproject.org2025-10-30T21:09:24Zurn:sha1:b7be042e020cb38ee817524f4a9d9f9187bed8f0
This code uses the algorithm of prop368: When a tunnel is
sufficiently isolated, we want to expire it after it has been
disused for a certain amount of time.
The implementation is a little tricky, since we need to call an
async function on ClientTunnel to look up the disused_since() check.
We don't want to call async functions while holding locks, so
we need to drop the TunnelList lock before we do the disused_since()
calls, and the grab it again.
As part of this change, I've had made expiration functions return
the earliest time at which any tunnel might expire. We can use
this in the future to spawn fewer expiration tasks, and scan the
list of tunnels less often.
circmgr: make expiration functions async2025-11-12T15:00:55ZNick Mathewsonnickm@torproject.org2025-10-30T17:24:00Zurn:sha1:0ed236bb45a6977bef5d317f3e596fdd0d0658a9
We'll need them to be async so they can call disused_since() on tunnels.
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
all: run cargo fmt2025-11-05T03:39:55ZSteven Engleropara@torproject.org2025-11-05T03:02:12Zurn:sha1:9bb8a888461473691085ea1bfc8fea0669d22e9call: replace all uses of `futures::task::SpawnExt` with `tor_rtcompat::SpawnExt`2025-11-05T03:39:55ZSteven Engleropara@torproject.org2025-11-05T03:00:47Zurn:sha1:6bfa9e986694b4fce0926dd21f309161e497ced8Remove "doc_auto_cfg" incantation from all crates.2025-09-29T19:30:03ZNick Mathewsonnickm@torproject.org2025-09-29T18:30:14Zurn:sha1:808b0ec2e3735a6dbbebeb857a3d6040ae02c697
This feature has been removed from nightly, in favor of doc_cfg.
Move `FallbackDir` into `tor-dircommon`2025-09-11T17:53:40ZClara Englercve@cve.cx2025-09-11T17:53:40Zurn:sha1:144cb860535273fed072a1ef6bc5684cf36ac31bproto: 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.
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.