mirrors/arti.git/crates/tor-config, branch arti-v2.4.0

Bump all the unstable tor- and arti- crates to 0.43.0

2026-06-01T16:32:03Z

Done using: ``` for crate in $(./maint/list-crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.43.0 done ```

Bump the versions of the non-{arti-,tor-} crates

2026-06-01T16:30:04Z

The non-{arti-,tor-} crates are: ``` ./maint/list-crates | rg -v '^(tor|arti)' oneshot-fused-workaround web-time-compat slotmap-careful test-temp-dir fslock-guard hashx equix caret fs-mistrust safelog retry-error futures-copy ``` We split them in the following categories: * crates with no changes (no version bumps): ``` oneshot-fused-workaround: No change. web-time-compat: No change. slotmap-careful: No change. test-temp-dir: No change. caret: No change. safelog: No change. retry-error: No change. futures-copy: No change. ``` Obtained with: ``` maint/changed-crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '$tor\|arti$-' ``` * crates that only have non-functional changes (bump the patch version, but not the dependend-on version): - equix * crates where functional changes were made, but no APIs were broken (bump patch): - fs-mistrust * crates where APIs were broken (bump minor): - hashx - fslock-guard The bumps from this commit were created using this script: ``` PATCH_NF=( equix ) PATCH=" fs-mistrust " MINOR=" hashx fslock-guard " ./maint/bump-nodep "${PATCH_NF[@]}" for crate in $PATCH; do cargo set-version --bump patch -p $crate; done for crate in $MINOR; do cargo set-version --bump minor -p $crate; done ```

config: Simplify ConfigurationTree::merge_from to take &mut self.

2026-05-27T12:05:52Z

Apply 3 suggestion(s) to 2 file(s)

2026-05-27T12:05:52Z

Co-authored-by: gabi-250

config: Update doctests to use Deftly, and to pass

2026-05-27T12:05:52Z

Some of the tests used derive(Builder), which is not current practice for our configuration. Additionally, they didn't implement the requisite ConfigBuilder logic to pass with the other changes in this branch.

Give resolve_return_results options to control output_tree.

2026-05-27T12:05:52Z

I've left the options here as booleans, but moved them into a struct. (IMO, booleans are at their riskiest when they are passed as function arguments, and much less risky when they are used as struct fields.)

config: Add an `output_tree` to our resolver methods.

2026-05-27T12:05:52Z

This functionality exposes the part of the configuration tree that was actually used, along with any defaulted values. RPC will want this.

config: Add a dd(TorConfig) attribute to override apply_defaults().

2026-05-27T12:05:52Z

config: Add a method to fill in a builder with unset defaults

2026-05-27T12:05:52Z

This new method modifies a builder by replacing any unset values that have a default with that default. We're using this method so that we can re-serialize a builder into a `ConfigurationTree` with all of its default values included. In all cases, `b.apply_defaults()?; b.build()` should produce the same output as `b.build()`. The interesting parts of this commit are in tor_config::load and tor_config::derive. The rest of this commit just adds `apply_defaults` to other builders that _aren't_ made with `derive_deftly(TorConfig)`.

config: Implement Builder for ListBuilders and MapBuilders.

2026-05-27T12:05:52Z

This isn't strictly necessary, but it helps for consistency.