mirrors/arti.git/crates/arti-relay/src/builder.rs, branch arti-v1.3.2

arti-relay: Rename remaining XXXs to be TODOs

2024-10-10T17:48:42Z

Signed-off-by: David Goulet

arti-relay: Remove the use of pub and pub use

2024-10-10T15:12:32Z

The "pub" and "pub(crate)" visibility in a binary crate is essentially the same except for the dead_code warning analysis which ignores "pub" but will warn at "pub(crate)". This should get fixed soon according to: https://github.com/rust-lang/rust/issues/74970 However, for now, lets catch all this dead code :). Part of #1674 Signed-off-by: David Goulet

arti-relay: Remove its library crate

2024-10-10T15:12:32Z

Simply, the lib.rs is renamed to relay.rs (containing TorRelay object) so this crate can never be used as a library. This is important because at the moment, we don't want to have a relay stable API that can be used to embed relays in applications. Closes #1674 Signed-off-by: David Goulet

arti-relay: add and use `Error`/`ErrorDetail`

2024-09-05T19:51:16Z

Most of this is copied from `arti_client::err`, but with a lot of stuff removed to simplify the error types (for example no `error_detail` feature handling). I tried to keep things generally consistent with arti-client so that error handling will be similar in both crates. `TorRelayBuilder::create()` will likely need to be fallible in the future (for example if spawning a task for the OR port listener fails), so it now returns a `Result` instead of just a `TorRelay`.

arti-relay: pass config in `TorRelay::create_inner`

2024-09-03T22:23:08Z

relay: Add basic configuration and builder

2024-08-20T13:09:31Z

This adds the basic TorRelayConfig object along a builder in order to create a TorRelay object. At this commit, the configuration object only holds a "StorageConfig" which is a simple starting point which will allow to expand to a KeyMgr and then a ChanMgr along more configuration. There is also no custom Error for the crate at this point. Fixes #1534 Signed-off-by: David Goulet