mirrors/arti.git/crates/tor-dirmgr/src/state.rs, branch derive-traitsmirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=derive-traits2022-02-23T18:56:52Zdirmgr::Store.expire_all takes config2022-02-23T18:56:52Ztharviktharvik@users.noreply.github.com2022-02-11T12:02:35Zurn:sha1:b28803d861030c56b8d77deacbfc9fd29746bb27dirmgr: add Store trait2022-02-23T18:50:33Ztharviktharvik@users.noreply.github.com2022-02-03T15:35:40Zurn:sha1:8658052ce3c4c65fb8cfdc41dab5ead681dc3e9fdirmgr: Remember where netdocs came from.2022-02-16T21:28:23ZNick Mathewsonnickm@torproject.org2022-02-16T21:28:23Zurn:sha1:2a7087ff93eecb94946a73a72d24659b85217efa
This isn't complete (see TODO), but it's enough to let us report the
right ErrorKind if something fails to parse.
dirmgr: eliminate StringParsingError.2022-02-16T21:02:28ZNick Mathewsonnickm@torproject.org2022-02-16T21:02:28Zurn: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.
dirmgr: HasKind for internal and sqlite errors2022-02-16T20:48:24ZNick Mathewsonnickm@torproject.org2022-02-16T20:48:24Zurn:sha1:f71473cf73a84afd0606817665e5b27fa290584d
At first I had thought that all sqlite errors would be internal, but that's
not the case.
Fix test failure in tor_dirmgr::state::test::get_microdescs_state2022-01-27T22:13:38ZNick Mathewsonnickm@torproject.org2022-01-27T22:13:38Zurn:sha1:98d81716105c3bc90256a7b1533071c92d9594e1
This failure occurred because our tests use canned data to exercise
the directory state functionality, and the canned consensus has
suddenly become very expired.
There are better fixes possible, but this is a minimal one that
should get CI working on main again.
bootstrap reporting: Documentation fixups from review.2022-01-19T13:22:42ZNick Mathewsonnickm@torproject.org2022-01-19T13:22:42Zurn:sha1:d1c362f30873f4f937d0452fdd5d804948622770tor-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.
Fixup broken doc comment from arti!2202022-01-10T15:10:41Zetator@eta.st2022-01-10T15:10:41Zurn:sha1:de1b19c22a60aa7e86c56023b65b14722ac33c05
That's what I get for blindly trusting @nickm :p
Merge branch 'ticket_178' into 'main'2022-01-10T14:02:24Zetator@eta.st2022-01-10T14:02:24Zurn:sha1:da848a1b9cb4cf6b829f24a4b7b994ba9e60b6ae
Fix ticket 178: Don't use a NetDir until we have microdescriptors for all of our primary guards.
Closes #178
See merge request tpo/core/arti!220