mirrors/arti.git/crates/arti-client/Cargo.toml, branch arti-v0.2.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.2.02022-04-01T13:15:18ZBump all arti*, tor* crates to 0.2.02022-04-01T13:15:18ZNick Mathewsonnickm@torproject.org2022-04-01T13:15:18Zurn:sha1:5b2fc118df0524144e6b2c34fdcce3d0fb692d24
Not all of these strictly need to be bumped to 0.2.0; many could go
to 0.1.1 instead. But since everything at the tor-rtcompat and
higher layers has had breaking API changes, it seems not so useful
to distinguish. (It seems unlikely that anybody at this stage is
depending on e.g. tor-protover but not arti-client.)
Reformat several Cargo.toml files with 100-char-wide lines.2022-03-30T14:41:40ZNick Mathewsonnickm@torproject.org2022-03-29T17:39:03Zurn:sha1:1feb7eecacf0718f46a36175b75ffdcc152b340cTurn FallbackList into a real type, and store one in GuardMgr.2022-03-30T14:39:06ZNick Mathewsonnickm@torproject.org2022-03-25T20:44:12Zurn:sha1:9da43189f36b19681d10b78ef982c52c929b4573
The guard manager is responsible for handing out the first hops of
tor circuits, keeping track of their successes and failures, and
remembering their states. Given that, it makes sense to store this
information here. It is not yet used; I'll be fixing that in
upcoming commits.
Arguably, this information no longer belongs in the directory
manager: I've added a todo about moving it.
This commit will break compilation on its own in a couple of places;
subsequent commits will fix it up.
Merge branch 'dir-filter' into 'main'2022-03-25T15:59:54ZIan Jacksoniwj@torproject.org2022-03-25T15:59:54Zurn:sha1:565a3d1d01b5b93c1e68d87e1a1d66f42fbcf41b
arti-client, dirmgr: Initial DirFilter code
See merge request tpo/core/arti!431Expose DirFilter from arti-client.2022-03-24T16:10:46ZNick Mathewsonnickm@torproject.org2022-03-24T16:07:07Zurn:sha1:123cd2223bc5b6e22a537bfa2f3a5cb1cd82e758
This will make it possible to implement a directory-munging
mechanism in arti-testing for #397.
Reformat {arti-client,tor-dirmgr}/Cargo.toml2022-03-24T16:10:35ZNick Mathewsonnickm@torproject.org2022-03-21T16:22:29Zurn:sha1:4354415999154edb70521fce22e23ebfd7512611Implement a periodic task scheduler, and a basic dormant mode2022-03-23T13:43:48Zetator@eta.st2022-03-23T13:43:48Zurn: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.
Merge branch 'config-partials-transparent' into 'main'2022-03-17T12:30:46ZIan Jacksoniwj@torproject.org2022-03-17T12:30:46Zurn:sha1:40bede587c8d9a0a29ad103832a9c9cd4a2f5982
Absolish builders for CircMgrConfig and DirMgrConfig
See merge request tpo/core/arti!417Change type of TorClientConfig::override_net_params2022-03-16T19:30:59ZIan Jacksonijackson@chiark.greenend.org.uk2022-03-16T18:25:06Zurn:sha1:8d54c0f0737654534806a34a9e8a738ab1fcd66f
Now we use NetParams. That implies making its constructor public,
which I think it fine.
This is related to #413 but is far from completing that ticket.
derive_builder: Switch to upstream 0.112022-03-16T16:34:44ZIan Jacksonijackson@chiark.greenend.org.uk2022-03-16T14:52:12Zurn:sha1:da787d074a04c97a1e28709f53f1cff5127b7ac9
This has the different syntax for builder field attributes than what I
originally proposed in my MR, and which therefore is in the pinned
branch.
My upstream MR for the field attributes feature was morged:
https://github.com/colin-kiegel/rust-derive-builder/issues/239