mirrors/arti.git/crates/arti/src/subcommands/proxy.rs, branch arti-v1.6.0

arti: Add skip_all to instrument call.

2025-09-24T19:23:32Z

arti: Add skip_all to instrument macro.

2025-09-24T19:23:32Z

It's unlikely these arguments will be particularly useful, and omitting skip_all can have security implications, so it's better to avoid it to reflect good practice.

opentelemetry: Add some instrument macros.

2025-09-24T19:23:32Z

I've added these in places that are useful for the debugging that I've been doing.

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.

arti: Optionally set up a Prometheus metrics exporter

2025-04-08T17:20:50Z

New cargo feature `metrics`, currently experimental. New config option `metrics.prometheus.listen`. Uses standard `Listen` syntax, but not every configuration is supported due to upstream limitations. If the config option is set, use metrics-exporter-prometheus to offer an HTTP scrape endpoint. Or, if compiled out, fail. Currently there are no actual metrics exported at all.

tor-rtcompat: Remove ToplevelBlockon from Runtime

2025-03-04T17:30:43Z

Introduce ToplevelRuntime as an alias, and use it in the top-level programs. Now none of the principal protocol implementation code has access to the executor's toplevel entrypoint, and can't call it by mistake.

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.

arti: Use connect points to listen for RPC connections.

2024-12-19T21:12:25Z

arti-client: add path resolver to `TorClient` and `TorClientConfig`

2024-11-18T15:01:56Z

Rather than using `arti_client::config::path_resolver()`, third-party code can get the path resolver using `TorClientConfig`s `AsRef` impl instead.

update `CfgPath::path` to use a `CfgPathResolver`

2024-11-18T15:01:56Z

This is a big change across multiple crates since there isn't a good way to break it up. This changes the signature of `CfgPath::path` to: ``` pub fn path(&self, path_resolver: &CfgPathResolver) -> Result { ``` Making this change means that our global `CfgPathResolver` needs to be stored in the 'arti-client' library instead of `tor-config-path`, and must be passed through to anything that calls `path` to expand the variables.