mirrors/arti.git/crates/tor-ptmgr/src, branch arti-v1.3.1

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

tor-config: removed re-export of `CfgPath`

2024-11-04T14:58:43Z

Also updated other packages to get `CfgPath` directly from `tor-config-path' instead of 'tor-config'.

Use mpsc_channel_no_memquota next to a TODO

2024-10-15T11:03:18Z

We have a ticket for this. But the ticket number was wrong, so fix that.

memquota: Note a TODO about PT channels

2024-10-02T15:05:12Z

ptmgr: Forbid managed pts on non-localhost

2024-09-25T16:42:45Z

ptmgr: Warn on non-local unmanaged PTs

2024-09-25T16:35:40Z

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: break out `spawn_transport` into separate function

2024-08-20T14:06:56Z