mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.2.0 2022-03-30T12:44:25Z 2022-03-30T12:44:25Z eta tor@eta.st 2022-03-30T12:44:25Z urn:sha1:fd081742fa13e8464ad46123d83617165587d4f4 Don't use SystemTime::now() Closes #306 See merge request tpo/core/arti!365 2022-03-24T14:07:40Z eta tor@eta.st 2022-03-24T14:07:40Z urn:sha1:ee47a16697d93cfd49a0b44669831713dbe7f63f Addressing review comments: added some unit tests for the new scheduler type, and made FireIn use an Instant instead (making it FireAt). 2022-03-23T13:43:48Z eta tor@eta.st 2022-03-23T13:43:48Z urn:sha1:1ca79ff988d698b9bd8ec21fff12b8120cc17b28 This is a revised version of !397; it implements a scheduling system for periodic tasks that can be externally controlled, and then uses the external control aspect to implement a basic dormant mode (#90). More technically, the scheduling system consists of a `Stream` that periodic tasks are expected to embed in a `while` loop or similar, a way for tasks themselves to choose how long to wait until the stream next yields a result, and a handle to control this outside of the task. 2022-03-14T20:19:20Z trinity-1686a trinity@deuxfleurs.fr 2022-03-11T17:27:59Z urn:sha1:f4581ffd0438a0e07839036f36960ad41742be03 2022-03-14T19:59:33Z trinity-1686a trinity@deuxfleurs.fr 2022-03-05T18:49:38Z urn:sha1:4a44ef56c0743775d49eca138a253f11e93c7a35 2022-03-01T20:38:05Z Nick Mathewson nickm@torproject.org 2022-03-01T20:38:05Z urn:sha1:83c8b11c2c08a05928bdb0390922391d13261ef2 Disable clippy::clone_on_ref_ptr See merge request tpo/core/arti!352 2022-03-01T13:16:02Z Nick Mathewson nickm@torproject.org 2022-03-01T13:16:02Z urn:sha1:57a8fe5f55beaab09e2f9b4a50dc2092885b5017 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-25T23:33:44Z trinity-1686a trinity@deuxfleurs.fr 2022-02-25T23:33:44Z urn:sha1:f06b25601006ba42c427349837dca6d5634bc718 2022-02-25T17:34:05Z eta tor@eta.st 2022-02-25T17:34:05Z urn:sha1:387ebda740081983cf1f051c630a7729dc6e7926 `PreferredRuntime` is now an opaque wrapper struct that contains the "actual" preferred runtime as a type alias. The `current_user_runtime` and `create_runtime` functions become `PreferredRuntime::current` and `PreferredRuntime::create`, respectively. This removes the dependence on `impl Trait`, meaning we can now name the returned runtime (yay!). In addition, the documentation was cleaned up a bit to make it (hopefully) flow better. Items that don't make sense to publicize, like testing implementation details, have been marked #[doc(hidden)] and semver warnings added.