mirrors/arti.git/crates/tor-netdoc/src/doc/netstatus/build, branch arti-v1.8.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.02025-11-18T19:50:23ZRelayFlags: Use RelayFlag enum variant names everywhere2025-11-18T19:50:23ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-18T18:55:10Zurn:sha1:c37e44403416b7f1abbd62d080b698da35d04537
Abolish the constants with the transitional names.
This also abolishes the controversial name `H_S_DIR`, which Rust case
transformation rules generated from `HSDir`.
RelayFlags: Use the singular RelayFlag for naming individual flags2025-11-18T19:44:21ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-18T18:36:08Zurn:sha1:3245738729e1d93be48485f2877a9e17ba2e7f28
We're going to separate RelayFlag from RelayFlags.
We could continue to provide a bunch of constant values for
RelayFlags, for each individual type, but that would involve an ad-hoc
derive, and would still be a bit of an unusual API.
Instead, we're going to make ``RelayFlag` a normal enum.
In this commit, we change everyone to refer to it by its singular
name. Hopefully separating out this bulk change makes both this, and
the core commit, easier to review.
tor-netdoc: Introduce DocRelayFlags for relay flags in a network document2025-11-18T17:06:51ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-23T14:12:44Zurn:sha1:3dfea170e26a9d9f140830b418eca3191b337fb0
This will have space for unknown flags.
tor-netdoc: Rename RelayFlags elements for regularity vs spec2025-11-18T17:06:51ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-23T13:35:07Zurn:sha1:f7317d7068884860c1d1a69e30eca962ee7da827
Add underscores so that the spec keywords and the flag constants
correspond (according to `paste`'s case-changing rules).
Fix name of clippy lint to unchecked_time_subtraction (2)2025-11-06T11:28:22ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-06T11:23:25Zurn:sha1:a5fd5c48ea059a80cc1f6c50e248654b5ff3aaff
Run maint/add_warning
tor-netdoc: Preamble: rename relay_version field to server_version2025-10-22T13:18:04ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-21T16:17:33Zurn:sha1:56929533b5e39e64c85b1697a5f9dcd4cd2d4193
This makes it match the protocol and the spec.
tor-netdoc: netstatus: Preamble: rename shared rand fields to match doc2025-10-22T13:17:51ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-21T11:43:09Zurn:sha1:ac9af3273f12585bab50857f19124047098d2ff9
We should use the same name everywhere, even if the name in the spec
is clumsy (as it is here).
tor-netdoc: Move ConsensusFlavor into Consensus struct2025-10-22T13:17:51ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-20T11:18:22Zurn:sha1:739f40ba7d628d2c860c141e1b093e2f0c6e3125
We're going to want to apply the parse2 derive to Preamble, but this
field is anomalous. Rather than trying to make it regular, simply
move it to the old-parser-specific Consensus struct.
tor-netdoc: Rename consensus Header to Preamble2025-10-22T13:17:51ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-20T11:06:08Zurn:sha1:009315256130d4c0150795844f927e07e52cc16e
There is no such thing as the "header" according to the spec. We mean
the preamble.
tor-netdoc: Change type of timestamp in SharedRandStatus2025-10-21T15:23:48ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-21T15:15:42Zurn:sha1:3481970f543619b4b64ec3784136f7dc4b1455c6