mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=derive-traits 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-17T20:12:00Z Nick Mathewson nickm@torproject.org 2022-02-17T20:12:00Z urn:sha1:64a0d4dce54199c2c3752d48e91a5118bb898b91 Getting a non-200 status is no longer a failure condition; it's just a different kind of answer. Closes #349. 2022-02-16T21:02:28Z Nick Mathewson nickm@torproject.org 2022-02-16T21:02:28Z urn:sha1:4bb7c973991ec48178bf2371727def1f1d912e95 It had too many possible Kinds depending on what kind of string had failed to parse. I decided to use #[source] here instead of #[from], so that we would have to explicitly convert these errors where they show up. 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