mirrors/arti.git/crates/tor-guardmgr/src/pending.rs, branch arti-v2.5.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.02026-03-26T19:20:17Ztor-guardmgr: Port to web_time_compat.2026-03-26T19:20:17ZNick Mathewsonnickm@torproject.org2026-03-26T15:06:10Zurn:sha1:02421eae87ee34653960046c25b6239b01f557c9Switch Cargo.toml files to edition 2024.2025-08-07T15:28:36ZNick Mathewsonnickm@torproject.org2025-08-06T01:19:58Zurn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
extract 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:0f189093db1e49042827ae4d09bbb4bd93e966ccCreate and use API to report guard/fallback skew.2022-04-07T14:47:45ZNick Mathewsonnickm@torproject.org2022-04-06T13:05:35Zurn:sha1:c3c43b088e9f8dcbe876c277c3af14705244e8b0
(The information is not yet recorded.)
Refactor FirstHopId into type-differentiated form2022-03-30T14:41:39ZNick Mathewsonnickm@torproject.org2022-03-29T14:55:20Zurn:sha1:6282df34fb00c3b8b686553e05f8d3172b017ed0
The FirstHopId type now records an enum that stores whether the hop
is a guard or a fallback. This change addresses concerns about
remembering to check the type or source of an Id before passing it
down to the FallbackState or GuardSet.
Making this change required an API change, so that dirmgr can
report success/failure status without actually knowing whether it's
using a fallback or a guard.
Rename Guard=>FirstHop, GuardId=>FirstHopId2022-03-30T14:40:59ZNick Mathewsonnickm@torproject.org2022-03-29T13:05:39Zurn:sha1:13af6134f6180f7241daca9206fa49ed5f26829d
This is preparation for having separate GuardId and FirstHopId types
that distinguish which back-end they index.
Clarify documentation about GuardUsable constructors2022-03-30T14:40:14ZNick Mathewsonnickm@torproject.org2022-03-29T12:21:11Zurn:sha1:c721c8ee534b49e960622741307bdca6e613a403Add a TODO about an unslightly type.2022-03-30T14:40:14ZNick Mathewsonnickm@torproject.org2022-03-29T12:20:53Zurn:sha1:16ce29ef59116f13e7e2aa181d05200edc1f6aff