mirrors/arti.git/crates/tor-guardmgr/src/daemon.rs, branch arti-v1.3.2mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.22024-08-28T14:27:46Zextract tor_async_utils::oneshot into ::oneshot-fused-workaround2024-08-28T14:27:46ZJim Newsomejnewsome@torproject.org2024-08-22T19:20:36Zurn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1
Having this in the `tor-async-utils` crate prevents us from doing both
of the following without introducing a circular dependency:
* using it in `tor-rtmock` (which we currently do, particularly in
tests).
* using `tor-rtmock` to test things in `tor-async-utils`. We don't do
this yet, but it is generally sensible to do so. In particular we
want to move the `stream_peak` module there, which is currently tested
with `tor-rtmock`.
Moving this into its own crate avoids this circular dependency.
oneshot: Apply deferred rustfmt churn2023-10-11T15:19:46ZIan Jacksonijackson@chiark.greenend.org.uk2023-10-11T15:09:09Zurn:sha1:665ba4f6b6ed2de6f723177d5472e7ee1440599e
cargo fmt, precisely.
oneshot: Use veneer in tor-guardmgr2023-10-11T15:19:21ZIan Jacksonijackson@chiark.greenend.org.uk2023-10-11T14:09:26Zurn:sha1:0f189093db1e49042827ae4d09bbb4bd93e966ccGuardMgr: Add Instant to update().2022-11-16T14:56:51ZNick Mathewsonnickm@torproject.org2022-11-16T14:46:21Zurn:sha1:76a89fb178d747255e3b993ff2521e487b4db06f
This lets us avoid calling `Instant::now()`, when `Runtime::now()`
is what we want.
Unfortunately, there are a bunch of functions that called `update()`
that needed to change. Fortunately, none of the changes were very
complicated.
Fixes a `TODO pt-client` comment.
GuardMgr: Launch a background task to keep the list of bridge2022-11-08T13:10:15ZNick Mathewsonnickm@torproject.org2022-11-04T14:27:37Zurn:sha1:d395ae75a54c14e889b577e10869bb1ccd94bbd0
descriptors updated as appropriate.
GuardMgr: Exit keep-netdir-updated task early if GuardMgr disappears.2022-11-08T13:10:15ZNick Mathewsonnickm@torproject.org2022-11-04T14:24:11Zurn:sha1:e93ee142709c25a10d7d3964afd6f28e58fa7dddRefactor external guardmgr APIs: Stop taking NetDir arguments.2022-11-08T13:10:15ZNick Mathewsonnickm@torproject.org2022-11-02T17:54:00Zurn:sha1:95a95076a77f44478736464a6249bee345713ecc
These arguments were used only for legacy (testing) purposes; the
tests now use `TestNetDirProvider`. This lets us simplify our
internal logic for passing a `NetDir` to our samples, and prepare
for having a `BridgeSet` to pass there instead.
This is a breaking change to `guardmgr` and `circmgr`.
GuardMgr: Update to use new NetDirProvider API.2022-07-26T09:41:06ZNick Mathewsonnickm@torproject.org2022-07-25T15:56:10Zurn:sha1:0bca4d825cfa6995ce275b4113a48601e3fdb9dcMove responsibility for GuardMgr NetDir updates to GuardMgr.2022-06-07T15:44:51ZNick Mathewsonnickm@torproject.org2022-06-02T21:35:01Zurn:sha1:dc0a4e3c3d20bb6708a1e20df1c07a78041b6111
Previously it was the job of a task in CircMgr to do this; but we're
going to want to give GuardMgr full access to the latest NetDir for
this, and for other code-simplification reasons.
With this change I'm deprecating a couple of functions in
tor-circmgr. It's no longer necessary for us to have an artificial
external way for you to feed new NetDirs to a circmgr. (I could
just remove them, but I want practice deprecating.)
GuardMgr: record clock skew information.2022-04-07T15:33:34ZNick Mathewsonnickm@torproject.org2022-04-07T15:30:08Zurn:sha1:99146da2c2654c01259b8219bd491c5d4ac47039
(It is not yet actually used.)