mirrors/arti.git/crates/tor-ptmgr/src/managed.rs, branch arti-v1.3.2

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.

tor-ptmgr: pass through the `CfgPathResolver`

2024-11-18T15:01:56Z

extract tor_async_utils::oneshot into ::oneshot-fused-workaround

2024-08-28T14:27:46Z

Having this in the `tor-async-utils` crate prevents us from doing both of the following without introducing a circular dependency: * using it in `tor-rtmock` (which we currently do, particularly in tests). * using `tor-rtmock` to test things in `tor-async-utils`. We don't do this yet, but it is generally sensible to do so. In particular we want to move the `stream_peak` module there, which is currently tested with `tor-rtmock`. Moving this into its own crate avoids this circular dependency.

tor-ptmgr: added a 'managed-pts' default feature

2024-08-21T17:17:50Z

This conditionally compiles most of the code related to managed transports.

tor-ptmgr: move some code to a new 'managed' module

2024-08-20T14:05:50Z

Code that's related to managed transports has been moved to a new 'managed' module. This includes the PT reactor since it's not needed for unmanaged transports.