mirrors/arti.git/crates/tor-dirmgr/src/lib.rs, branch arti-v0.0.4mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.42022-01-18T18:06:08Ztor-dirmgr: Create a bootstrap-status exporting mechanism.2022-01-18T18:06:08ZNick Mathewsonnickm@torproject.org2022-01-13T18:55:34Zurn: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.
extend lints to include 'clippy::all'2021-12-28T20:15:40ZDaniel Eadesdanieleades@hotmail.com2021-12-28T20:15:40Zurn:sha1:592642a9e6c1c03e525f8b452f4b97e6fd17ff9bRefactor directory events to use a FlagPublisher mechanism.2021-12-14T19:05:02ZNick Mathewsonnickm@torproject.org2021-12-09T19:10:41Zurn: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.
Add a few tests to tor-config.2021-12-08T00:52:49ZNick Mathewsonnickm@torproject.org2021-12-08T00:52:49Zurn:sha1:b3b6a92145380ebe685bd2410db32fdee4a97e9bMake override_net_params take effect sooner.2021-12-08T00:26:01ZNick Mathewsonnickm@torproject.org2021-12-08T00:22:54Zurn:sha1:42ae8c7a2ad776cfdc54c9587a3381a8a3189740
This is still not as soon as I'd like: a real change here will require
refactoring DirMgr::notify().
Make much of DirMgrConfig reconfigurable.2021-12-07T22:36:16ZNick Mathewsonnickm@torproject.org2021-12-07T22:36:16Zurn: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.
Sketch API for reconfiguration.2021-12-07T20:42:14ZNick Mathewsonnickm@torproject.org2021-12-06T18:54:53Zurn:sha1:606d64eac5936a9f0bfec32b8b5a85f3dea77559
This patch doesn't actually make anything reconfigurable, but it
does create an API that will tell you "you can't change the value of
that!" If the API looks reasonable, I can start making it possible
to change the values of individual items.
Resolve roughly half of the XXXXs.2021-12-06T20:11:03ZNick Mathewsonnickm@torproject.org2021-12-06T20:01:29Zurn:sha1:31b385c5b20205e879a847a9331c30a37dc2e6f5
We want to only use TODO in the codebase for non-blockers, and open
tickets for anything that is a bigger blocker than a TODO. These
XXXXs seem like definite non-blockers to me.
Part of arti#231.
dont warn on bootstrap error when error == manager dropped2021-11-30T11:50:27Zdagondagon12@tutanota.com2021-11-30T11:50:27Zurn:sha1:0122e1533998144015245e01509caac2f54f449fMerge branch 'config-updates-and-tests'2021-11-29T18:59:41ZNick Mathewsonnickm@torproject.org2021-11-29T18:59:41Zurn:sha1:eb861b7edd35fa60d1fb21a907400c42ab8e08fd