mirrors/arti.git/crates/tor-dirmgr/src, branch arti-v1.4.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.32025-04-16T23:06:51ZRename recommended_protocols to protocol_statuses.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-16T11:59:00Zurn:sha1:461a2467f90dbd2bf4f4b900fc0816aa4c906fdb
This name reflects its purpose better than the original one,
since it includes required protocols as well as recommended ones.
protover, *: Add documentation about what "supported" means.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-14T00:42:31Zurn:sha1:11148719ba04aab37c7784d198018eeacced69c2dirmgr: Always apply changes before advancing consensus.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-08T18:14:02Zurn:sha1:69f656c017b8ce7d804bc65dd1dac24b3aa94427
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.
Add warnings about removing supported protocols.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-07T15:27:42Zurn:sha1:ba612260ae603c8e5eba37206c21fd089afe075dnetdir: Add a recommended_protocols() to NetDirProvider2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-07T14:59:29Zurn:sha1:42e01549f946f5f23ab004fe2ed82fc9279d8e8ddirmgr, netdir: Store protocol requirments as soon as they are validated.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-03T15:20:32Zurn:sha1:98f28d0b4c5c2b90ed732ed29d571f71a48c15b4dirmgr: Backend support for cacheing protocol status.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-03T12:47:41Zurn:sha1:b483b454669b8b0ce93ea52896992d9234e4779d
We want to store this separately from the consensus,
because we want to access it very early in our load-from-cache
process, without checking the consensus that contains it
for timeliness.
New functions to report supported subprotocols2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-02T18:00:00Zurn:sha1:efe36d15de88ec5b7f39db99f9d2a58e4e5db7ac
Part of #1849.
Note that these functions are distributed across crates,
so that if (in the future) we stop doing API breaks
with every release, we will get the right outputs.
Note also that these functions build the list of protocols
out of specific symbolic features, rather than numbers:
this makes it easier to avoid errors about "which feature was
Relay=4 again", and easier to avoid accidentally referring to a
protocol that doesn't exist, like "Consensus" (should be "Cons")
or "HsDir" (case is wrong).
fix `clippy::doc_overindented_list_items`2025-04-03T17:32:58ZSteven Engleropara@torproject.org2025-04-03T17:21:49Zurn:sha1:663339ffa8bd00ce59c2dd39c288d338505263c3
Example:
```text
warning: doc list item overindented
--> crates/arti-rpc-client-core/src/conn/connimpl.rs:322:9
|
322 | /// indicates that no more messages will be received for this request.
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
note: the lint level is defined here
--> crates/arti-rpc-client-core/src/lib.rs:8:9
|
8 | #![warn(clippy::all)]
| ^^^^^^^^^^^
= note: `#[warn(clippy::doc_overindented_list_items)]` implied by `#[warn(clippy::all)]`
```
squash! Upgrade rand dependency to 0.9.2025-03-18T16:09:44ZNick Mathewsonnickm@torproject.org2025-03-18T14:47:35Zurn:sha1:895bc807f106e359d35522a3ad5f288ba6cf6a9c
- The Rng::gen() functions have been renamed to Rng::random().