mirrors/arti.git/crates/tor-dircommon/src, branch main

tor-dircommon: Sync + Send + 'static for DirBackendPlugin

2026-08-12T12:36:58Z

This commit adds marker traits as dependencies for implementations of the DirBackendPlugin trait, which will be required for intergration with hyper. Works like a charm, as DirMgr itself implements all three of these already.

dircommon: Add trait to use DirMgr as a temporary plugin

2026-08-10T17:18:51Z

This is part of #2657. The goal here is to use DirMgr as a temporary backend for tor-dirserver, so that we can have a sort-of-working directory cache that can be used for testing guards before tor-dirserver is complete.

tor-checkable: TimeRangeBound: Rename extend_tolerance to extend_end_bound

2026-07-23T10:13:34Z

It was confusing that one of these functions had "which bound" mentioned in its name, but the other didn't. So add `end` and switch from `tolerance` to `bound` (see previous commit message). *This* commit should deal only in `extend_tolerance` and `end` and shouldn't touch `extend_start_bound` or `extend_pre_tolerance`.

tor-checkable: TimeRangeBound: Rename extend_pre_tolerance to extend_start_bound

2026-07-23T10:13:34Z

Although it is often used to apply a tolerance, it doesn't make sense to say that this is extending the "tolerance" of a `TimeRangeBound`. A `TimeRangeBound` doesn't have a tolerance, only bounds. Also we should be consistent in our terminology, and use `start` rather than `pre`. We'll rename the other method too. Doing them one at a time will makes it easier to spot any "pre/start" vs "/end" slips: *this* commit should deal only in `pre` and `start` and shouldn't touch `extend_tolerance`.

Use new TimeRangeBound name throughout the tree

2026-07-16T15:47:50Z

add_warning: add reference to arti#2556

2026-07-15T17:56:49Z

Removed unnecessary lint

2026-07-15T17:16:51Z

Removed unnecessary lint

maint: Run maint/add_warning to deny string slices

2026-06-09T15:36:01Z

This commit executes maint/add_warning with the just added change to deny string slices except in tests. I recommend auditing this by checking out the previous commit followed by running the script yourself and then verifying that the diff is identical to this commit. This commit makes cargo clippy fail. We will add exceptions in the next commit.

dd(TorConfig): change the order of default vs magic

2026-05-27T12:05:51Z

This affects the automatic builder code made by our derive_deftly macro. It is only relevant (for now) in the case of the `NonZero<>` types and their special handling. Previously, when a builder contained Option, and we wanted to generate a configuration holding T, we would _first_ apply a transformation from Option to Option and _second_ unwrap the result or apply a default. Now, we _first_ convert from Option to U by applying a default, and only _then_ perform any necessary conversion from U and T. This is only relevant in the case where U and T are different. It simplifies writing the defaults for `NonZero` options, and will significantly simplify the logic for setting builder defaults.

dircommon: Port to use derive_deftly(TorConfig)

2026-02-17T13:49:49Z

Some of the behaviors of the existing types here are nonstandard; I've kept them and documented them, to avoid breaking compatibility.