mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.1.0 2022-02-23T18:50:33Z 2022-02-23T18:50:33Z tharvik tharvik@users.noreply.github.com 2022-02-03T15:35:40Z urn:sha1:8658052ce3c4c65fb8cfdc41dab5ead681dc3e9f 2022-02-17T19:22:47Z Nick Mathewson nickm@torproject.org 2022-02-17T19:22:47Z urn:sha1:83d001d66179e63978be632de0e15277f17a8228 2022-02-16T21:28:23Z Nick Mathewson nickm@torproject.org 2022-02-16T21:28:23Z urn:sha1:2a7087ff93eecb94946a73a72d24659b85217efa This isn't complete (see TODO), but it's enough to let us report the right ErrorKind if something fails to parse. 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-14T19:45:18Z eta tor@eta.st 2022-02-14T19:45:18Z urn:sha1:29daf5a74aa2ecef54047c2612243fb4207e2a53 Change deny(clippy::all) to warn(clippy::all). Closes #338 See merge request tpo/core/arti!306 2022-02-14T14:30:18Z Nick Mathewson nickm@torproject.org 2022-02-14T14:30:18Z urn:sha1:2cd4f0c872adba3b143573907b7aec61d0053e91 Found by nightly clippy. 2022-02-14T14:24:06Z Nick Mathewson nickm@torproject.org 2022-02-14T14:24:06Z urn:sha1:1cecc7e45a9a432f87a8f11abb8cb86b35464a0b Closes #338. 2022-02-11T16:42:19Z eta tor@eta.st 2022-02-09T16:27:34Z urn:sha1:882e75cd280ede6dc284f11db9e8f17947435ebe This commit changes how the `TorClient` type works, enabling it to be constructed synchronously without initiating the bootstrapping process. Daemon tasks are still started on construction (although some of them won't do anything if the client isn't bootstrapped). The old bootstrap() methods are now reimplemented in terms of the new create_unbootstrapped() and bootstrap_existing() methods. This required refactoring how the `DirMgr` works to enable the same sort of thing there. closes #293 2022-02-04T21:06:11Z Nick Mathewson nickm@torproject.org 2022-02-04T20:39:12Z urn:sha1:070e52653d9a49fe561e9ce119881f696baa325e (By our convention, these errors should say what we were trying to spawn when the error occurred.) 2022-01-18T18:06:08Z Nick Mathewson nickm@torproject.org 2022-01-13T18:55:34Z urn:sha1:f34faec7d96fdb87aa84744950ac37264b215965 The interface is similar to the one exposed by `arti-client`: it internally uses postage::watch to give a series of events showing when a bootstrap status is changing. Thanks to the existing state/driver separation in the DirMgr design we don't need much new logic: each download state needs to expose (internally) how far along it is in its download, which the bootstrap code passes to the DirMgr if it has changed. I believe that in the long run, we'll probably want to expose more (or different) information here, and we'll want to process it differently. With that in mind, I've made the API for `DirBootstrapStatus` deliberately narrow, so that we can change its of its internal later on without breaking code that depends on it. (The information exposed by this commit is not yet summarized in `arti-client`.) Part of #96.