mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.1.0 2022-03-01T13:08:56Z 2022-03-01T13:08:56Z Nick Mathewson nickm@torproject.org 2022-03-01T13:08:56Z urn:sha1:132416275d726c740f832eef70475d82f499b576 2022-03-01T10:28:06Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-03-01T10:16:28Z urn:sha1:bda9f82c551c76fe11ad2f4695d97bc4353d3a5a Fixed conflict in crates/arti-client/src/lib.rs as per tree from https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/364/#note_2782166 ie 13e55b8d7c22c26e55ba75823409b477f1bce66b 2022-02-28T19:29:50Z Nick Mathewson nickm@torproject.org 2022-02-28T19:29:50Z urn:sha1:9bf69f551ee5d05889cd449737f064448a5d6f30 2022-02-28T16:41:13Z eta tor@eta.st 2022-02-25T18:13:02Z urn:sha1:13ba0ea005ddd87bba2d53ab738ce948f031e1e8 This makes using the `PreferredRuntime` the first-class option inside `arti-client`, freeing users who don't want to think about runtimes from having to do so. `TorClient::create_unbootstrapped` and `builder` now automatically use this runtime, leaving only `builder_custom` for users who wish to manually specify a runtime. This lets us clean up the docs a lot: mentions of using custom runtimes are now relegated to nearer the end of the crate-level documentation, and we mostly just link to `tor_rtcompat`'s docs to explain more there. Instead, we take some more time to explain how you use the builder API to create clients synchronously. Other doc cleanups included getting rid of the explanation of `TorAddr` in the main crate-level doc; this is already well-documented elsewhere, and is something users should discover organically later. fixes arti#326 2022-02-25T18:05:25Z Nick Mathewson nickm@torproject.org 2022-02-25T18:05:25Z urn:sha1:489da37fe4f005e1ce0b0d35b88a33ed1a697f4e Otherwise, it's impossible to get a static sqlite linkage without also getting native-tls, even if you wanted rustls. Closes #302. 2022-02-24T19:55:59Z eta tor@eta.st 2022-02-18T16:02:18Z urn:sha1:c6fdd7c0037df821a7cfc475993322958c2f006a `StateMgr` got a new `unlock()` method that does what it says on the tin. We now call it from `bootstrap()` using the new `util::StateMgrUnlockGuard`, which works in a manner similar to the `BoolResetter` from `tor_dirmgr`. (A decent small little task in future might be to unify these types in some sort of general arti utility crate?) closes arti#335 2022-02-18T20:28:31Z Nick Mathewson nickm@torproject.org 2022-02-18T20:28:31Z urn:sha1:c910226b551a9ffc453e7f4baba0562d3a6d7bdc This is a defensive API choice to protect against the possibility that we'll want to add a bunch of other non-config options in the future. Closes #350 2022-02-16T19:29:16Z eta tor@eta.st 2022-02-16T15:57:24Z urn:sha1:790ea4af4bf5223ca81218d0f5508db2bd2db471 The new `BootstrapBehavior` enum controls whether an unbootstrapped `TorClient` will bootstrap itself automatically (`Ondemand`) when an attempt is made to use it, or whether the user must perform bootstrapping themselves (`Manual`). The `lazy-init` example shows how you could write a simple `get_tor_client()` function that used a global `OnceCell` to share a Tor client across an entire application with this API. closes arti#278 2022-02-14T14:24:06Z Nick Mathewson nickm@torproject.org 2022-02-14T14:24:06Z urn:sha1:1cecc7e45a9a432f87a8f11abb8cb86b35464a0b Closes #338. 2022-02-11T17:58:25Z Nick Mathewson nickm@torproject.org 2022-02-11T17:58:25Z urn:sha1:7da5d557bf6e870f9eb7fe048e5747969c0a803b (Looks like this one got missed.)