mirrors/arti.git/crates/tor-netdoc/src/doc/netstatus/rs.rs, 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-24T18:34:40Ztor-netdoc: Rename RelayFlagsParser to relay_flags::Parser2025-11-24T18:34:40ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-24T18:32:05Zurn:sha1:2df8bf8d3230671a0e049cb88af8903278c65381
Since we expose the relay_flags module, it makes sense to give this a
shorter name.
(It had a longer name when it was part of the netstatus module.)
tor-netdoc: relay_flags: Remove two now-not-needed type aliases2025-11-24T18:34:40ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-24T18:30:29Zurn:sha1:f27774d393ca14148e8ee6f93a220a392cddb1be
The generic parser type is easy enough to name now.
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: Separate ConsensusRelayFlagsParser and VoteRelayFlagsParser2025-11-18T17:06:51ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-10T16:50:39Zurn:sha1:a16441bb27dce19d42e1e04ad4fbff0f74b26d86
Provide a per-variety alias and use it for parsing; no longer impl
ItemValueParseable for RelayFlags.
tor-netdoc: Add a lot of spec cross-references and tidy docs2025-10-15T09:35:35ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-14T14:59:34Zurn:sha1:226d895a8dc374e652d71af4331f7c8e172a1b6e
Add links to torspec, and other cross-references.
Change heading fof `IgnoredPublicationTimeSp` to `publication` to
match spec and distinguish it from the `published` item in netstatus
docs.
Align several descriptions with the wording from torspec.
Remove a restatement of a fact from the spec, on the `valid_until`
field in `Lifetime`.
tor-netdoc: Type for parsing `m` lines in votes2025-10-15T09:35:35ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-09T13:08:56Zurn:sha1:5191e4a0581404fad1d89d282615e174a9a1d391tor-netdoc: RouterStatus: Add `publication` argument field2025-10-15T09:35:35ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-06T13:16:27Zurn:sha1:95fa35415ccfbff5ab5e8e5d0a91fcfd62b0f6cdtor-netdoc: RouterStatus: Split out the `r` item's fields2025-10-15T09:35:35ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-02T09:31:47Zurn:sha1:5e23bbb4c229cad738be29f77ffc95f8e8524c41
This makes the Rust structure closer to the document structure.
Arguably, this makes the Rust structure worse. But: I'm really very
keen on avoiding handwritten parsing and printing code. And, in the
longer term, having this linkage will hopefully apply pressure to
avoid further protocol complexity/variation/chaos.
tor-netdoc: No longer impl Sealed for RouterStatus (fmt)2025-08-26T09:53:24ZIan Jacksonijackson@chiark.greenend.org.uk2025-08-26T09:53:24Zurn:sha1:f823e1b17057a3710979747dd0477cd028f9be13