mirrors/arti.git/crates/tor-dirmgr/src/bootstrap.rs, branch arti-v1.8.0

opentelemetry: Instrument a bunch of functions.

2025-11-24T16:28:07Z

These are all aimed at figuring out in more detail what's going on in #2079 and related issues.

Fix name of clippy lint to unchecked_time_subtraction (2)

2025-11-06T11:28:22Z

Run maint/add_warning

tor-dircommon: Use amplify and getters for config

2025-09-09T14:42:18Z

Move `DownloadSchedule` into `tor-dircommon`

2025-09-08T16:46:32Z

This commit moves the `DowenloadSchedule` related types from `tor-dirmgr` into `tor-dircommon`.

misc: cleanup now that `_report!` macros support fields

2025-08-18T19:45:55Z

Switch Cargo.toml files to edition 2024.

2025-08-07T15:28:36Z

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.

tor-dirmgr: Removed dependency on `once_cell`

2025-06-15T02:11:18Z

- Replaced `once_cell::sync::Lazy` with `std::sync::LazyLock`. Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>

*: suppress cognitive_complexity warnings from nightly

2025-05-29T14:21:17Z

Apparently clippy nightly is better (or worse?) about detecting complex functions than before, so I'm suppressing these warnings where they occur. I have mixed feelings about these warnings: On the plus side, they really do help to detect functions that are twistier than they need to be. On the minus side, they get confused by tracing macros, and the "allows" do pile up. But on the plus side, those "allows" do provide a way to find functions that need to be refactored, and they are never uglier than the functions they decorate.

dirmgr: Always apply changes before advancing consensus.

2025-04-16T23:06:51Z

In the directory code, we have functionality to advance the consensus download state whenever possible, even if there is more we could download in the current state. That's fine, but when we're in this position, we need to be sure that we're taking any action based on the current state (such as installing notably parameters or, notably, protocol recommendations) before we move on.

squash! Upgrade rand dependency to 0.9.

2025-03-18T16:09:44Z

- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`