mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.4 2022-01-18T18:06:08Z 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. 2021-12-14T19:05:02Z Nick Mathewson nickm@torproject.org 2021-12-09T19:10:41Z urn:sha1:7f4578bec162c95da232a2f424abcd5ad55c9496 This approach tries to preserve the current interface, but uses a counter-based event backend to implement a coalescing stream of events that can be represented as small integers. The advantage here is that publishing events no longer needs to be a blocking operation, since there is no queue to fill up. 2021-12-07T22:36:16Z Nick Mathewson nickm@torproject.org 2021-12-07T22:36:16Z urn:sha1:e8ca0d7742e984381be130c01bf3ca0a4d20dd91 We can't change the authorities while in-flight: that would be pretty miserable to implement. Similarly we can't change the cache while in-flight. Everything else should be fair game, though there are a couple of tricky bits. I've tried to document those. 2021-11-25T13:20:37Z Daniel Eades danieleades@hotmail.com 2021-11-25T13:14:05Z urn:sha1:db16d13df4779ac61005050dfe5ce05e3d5a1b5d 2021-11-25T12:39:52Z Daniel Eades danieleades@hotmail.com 2021-11-25T12:39:52Z urn:sha1:052f51ff7115f362c2049c369c4f64864ab3412f 2021-11-18T17:33:08Z Nick Mathewson nickm@torproject.org 2021-11-18T17:33:08Z urn:sha1:96659a850be9efd6e7a48c6e6ce4d47dc8beef94 2021-11-12T11:54:50Z Dimitris Apostolou dimitris.apostolou@icloud.com 2021-11-12T11:35:28Z urn:sha1:ad3c18a456b469d4ccacbadd806aa45d6de4b517 2021-11-11T16:01:32Z Nick Mathewson nickm@torproject.org 2021-11-11T15:58:25Z urn:sha1:99aefe4bb8953fca9dbd4c476ce330b5fc38de38 It requires tracing-subscriber 0.2, which is a lower version than we want, and which causes trouble with our minimal-versions CI test. There is a pending issue to fix this; we can reinstate tracing-test once it is merged: https://github.com/dbrgn/tracing-test/pull/11 2021-11-11T13:58:48Z Nick Mathewson nickm@torproject.org 2021-11-11T13:58:48Z urn:sha1:4717bb270f2bd27130e636768a7bf6f3d450a9d3 2021-10-21T17:34:38Z Nick Mathewson nickm@torproject.org 2021-10-21T17:34:38Z urn:sha1:f3dc66d9646ae016dfad8808145d2d3249078d15