mirrors/arti.git/crates/tor-netdoc/src, branch arti-v1.3.1

PoW: Consolidate feature flags into a single flag.

2024-11-25T20:49:46Z

This replaces the hs-pow, hs-pow-full, hs-pow-v1, pow-v1, and pow-full features with a single hs-pow-full feature. It's possible that in the future we will want to split different schemes into different features, but we can do that when it comes up. For now, having this as a single flag makes it clearer what's going on, since the previous thing was not actually expressive enough to capture some things we care about (like "at least one pow scheme is enabled" that works in a future-compatible way). This change is not semver breaking since it's a experimental feature. Related: #1751

tor-netdoc: Error on PowParams::V1 when hs-pow-v1 is disabled.

2024-11-25T19:34:37Z

tor-netdoc: Don't include pow_params in HsDesc when feature is disabled.

2024-11-25T19:34:37Z

tor-netdoc: Support writing pow-params line.

2024-11-25T18:20:11Z

I'm not particularly happy with the code that does the actual writing out of the pow-params line, in particular the error handling there seems very verbose. However, I don't know of a better way to structure it given that APIs I'm working with.

TimerangeBound: Stop using std::ops::Bound.

2024-11-25T18:20:11Z

Fixes: #1691

tor-netdoc: add clippy allows and `#[non_exhaustive]`

2024-11-20T17:52:56Z

Disable a lot of dead code warnings

2024-10-17T10:25:24Z

Now cargo check --workspace --no-default-features --all-targets cargo build -p arti --no-default-features --features=memquota,tokio,native-tls are both clean.

Add a little test coverage for pow-params parsing.

2024-10-09T16:06:01Z

Cover some of the novel edge cases we're introducing around object parameters and repetition. This still feels awfully ad-hoc, but it's better than nothing. Co-authored-by: Micah Elizabeth Scott

hs-pow inner desc: broaden pow-params rule, disallow object for v1.

2024-10-09T16:06:01Z

We should not be restricting pow-params to occur only once at the rule level, and we shouldn't be disallowing object parameters at that level either. Instead, the v1 scheme itself needs to check for and disallow objects. Future schemes may allow object parameters. Test cases for this will be added in a subsequent commit. Co-authored-by: Micah Elizabeth Scott

Fix incorrect doc comment.

2024-10-09T16:06:01Z

Looks like a copy/paste error. Co-authored-by: Micah Elizabeth Scott