mirrors/arti.git/crates/arti/src/rpc.rs, branch arti-v2.1.0

arti: Fix some visibility-based compilation errors.

2026-02-24T13:05:39Z

arti: Port rpc configuration to dd(TorConfig).

2026-02-24T13:05:39Z

arti: Extract responsibility for port listing.

2026-02-19T17:01:09Z

Instead of doing this when we construct the listeners, we can do it in a separate method, to simplify the return type.

Fix name of clippy lint to unchecked_time_subtraction (2)

2025-11-06T11:28:22Z

Run maint/add_warning

all: replace all uses of `futures::task::SpawnExt` with `tor_rtcompat::SpawnExt`

2025-11-05T03:39:55Z

arti: Revise strings that implied that we were a SOCKS-only proxy.

2025-10-28T14:11:16Z

Closes #2225

Fix warnings and errors from edition 2024.

2025-08-07T15:28:39Z

The two main causes of errors were: - Since some of the lifetime rules have changed, we no longer need to do as many "bind a variable and immediately return it" patterns, and so clippy now warns about them. - We needed to adjust the explicit captures (`use<...>`) in a couple of our RPIT instances.

Switch Cargo.toml files to edition 2024.

2025-08-07T15:28:36Z

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.

*: suppress cognitive_complexity warnings from nightly

2025-05-29T14:21:17Z

Apparently clippy nightly is better (or worse?) about detecting complex functions than before, so I'm suppressing these warnings where they occur. I have mixed feelings about these warnings: On the plus side, they really do help to detect functions that are twistier than they need to be. On the minus side, they get confused by tracing macros, and the "allows" do pile up. But on the plus side, those "allows" do provide a way to find functions that need to be refactored, and they are never uglier than the functions they decorate.

arti: Make Rpc argument unconditional when constructing socks proxy

2025-01-23T17:25:41Z

Formerly this was a conditional method argument, which is a huge antipattern. Now it is unconditionally present, as `Option` for a type that is uninhabited when RPC isn't supported.