summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | tor-netdoc: ConsensusFooterFields: Constructor, parse, encodeIan Jackson2026-05-273-3/+14
| | | | |
| * | | | tor-netdoc: ConsensusFooterFields: Tidy docsIan Jackson2026-05-271-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | Add links to the spec, and delete explanatory text (that ought to be in the spec, not here).
| * | | | tor-netdoc: ConsensusFooterFields: Rename weights field to bandwidth_weightsIan Jackson2026-05-274-6/+7
| | | | | | | | | | | | | | | | | | | | This matches the spec.
| * | | | tor-netdoc: Rename Footer to ConsensusFooterFieldsIan Jackson2026-05-275-11/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will allow us to include this, conditionally, in the new per-variety footer types for consensuses, without too much disruption to the existing code. We don't leave a compatibility alias because we're going to want a Footer in each_variety.rs which is the actual sub-document. This old struct isn't suitable because it doesn't have the intro item and is just for consensuses.
| * | | | tor-netdoc: NetworkStatusVersion, replacing poc's with FixedStringIan Jackson2026-05-273-11/+15
| | | | |
| * | | | tor-netdoc: Provide FixedString and defined_fixed_stringIan Jackson2026-05-273-1/+146
| | | | | | | | | | | | | | | | | | | | We're going to want quite a lot of this for eg network-status-version.
* | | | | Merge branch 'client_typestate' into 'main'Nick Mathewson2026-05-277-230/+482
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Client: Refactor most managers into a typestate, and construct it on bootstrap. See merge request tpo/core/arti!4011
| * | | | | Apply 2 suggestion(s) to 1 file(s)Nick Mathewson2026-05-271-2/+2
| | | | | | | | | | | | | | | | | | Co-authored-by: gabi-250 <[email protected]>
| * | | | | client: Have launch_onion_service instantiate RunningInner as needed.Nick Mathewson2026-05-261-4/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Otherwise we either lose the property that you can call launch_onion_service before bootstrapping has begun, or we have to make launch_onion_service async.
| * | | | | client: RunningInner::reconfigure: refactor running → selfNick Mathewson2026-05-262-43/+81
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (This is a separate commit in order make the code movement in the previous commit clearer.)
| * | | | | client: Move dirmgr_store back into ClientShared.Nick Mathewson2026-05-261-9/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will ensure that the TorClient takes its file locks immediately on construction.
| * | | | | client: Fold wait_for_bootstrap{,_running} into a single method.Nick Mathewson2026-05-261-20/+14
| | | | | |
| * | | | | client: change remaining wait_for_bootstrap user.Nick Mathewson2026-05-261-5/+6
| | | | | |
| * | | | | client: Defer creation of most structures until bootstrap.Nick Mathewson2026-05-262-127/+226
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will let us be more confident in the inertness of a not-bootstrapping TorClient, _and_ make it easier to reconfigure things before the client is started.
| * | | | | client: Rename create_inner to create_implNick Mathewson2026-05-262-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now that we have a type called "inner", and will soon have a function to create it, we really don't want to retain this name.
| * | | | | client: move bootstrap lock to the head of bootstrap_inner.Nick Mathewson2026-05-261-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We want this look to cover the whole function, to avoid weird duplicate behavior while creating our bridge desc manager.
| * | | | | client: Factor out the "running a client" code into an inner typestateNick Mathewson2026-05-265-91/+186
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We'll use this to distinguish "not running" from "running", in order to make it easier to be sure that non-bootstrapping clients will definitely not try to connect to the network.
| * | | | | client: rename ClientInner → ClientShared.Nick Mathewson2026-05-261-5/+5
| | | | | |
* | | | | | Merge branch 'rpc_config_part1_v3' into 'main'Nick Mathewson2026-05-2716-65/+365
|\ \ \ \ \ \ | |_|/ / / / |/| | | | | | | | | | | | | | | | | Implement configuration backend logic for RPC See merge request tpo/core/arti!4001
| * | | | | config: Simplify ConfigurationTree::merge_from to take &mut self.Nick Mathewson2026-05-272-8/+9
| | | | | |
| * | | | | Apply 3 suggestion(s) to 2 file(s)Nick Mathewson2026-05-272-3/+3
| | | | | | | | | | | | | | | | | | Co-authored-by: gabi-250 <[email protected]>
| * | | | | config: Update doctests to use Deftly, and to passNick Mathewson2026-05-273-16/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.Nick Mathewson2026-05-273-15/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.Nick Mathewson2026-05-271-5/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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().Nick Mathewson2026-05-271-1/+36
| | | | | |
| * | | | | config: Add a method to fill in a builder with unset defaultsNick Mathewson2026-05-2712-1/+155
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)`.
| * | | | | tor-basic-utils: Add an if_empty helper macroNick Mathewson2026-05-271-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need this pattern in a lot of places; we might as well just define it once.
| * | | | | config: Implement Builder for ListBuilders and MapBuilders.Nick Mathewson2026-05-272-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | This isn't strictly necessary, but it helps for consistency.
| * | | | | dd(TorConfig): change the order of default vs magicNick Mathewson2026-05-272-23/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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<U>, and we wanted to generate a configuration holding T, we would _first_ apply a transformation from Option<U> to Option<T> and _second_ unwrap the result or apply a default. Now, we _first_ convert from Option<U> 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.
| * | | | | config: Fix documentation of ResolutionResultsNick Mathewson2026-05-271-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | It previously referred to a function that didn't exist.
| * | | | | tor-basic-utils: Correct documentation for macro_first_nonempty.Nick Mathewson2026-05-271-5/+5
| |/ / / / | | | | | | | | | | | | | | | | | | | | It looks like we renamed this macro, but didn't rename it in its documentation.
* | | | | Merge branch 'rd-bandwidth' into 'main'Ian Jackson2026-05-273-0/+29
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Add Bandwidth support to Router Descriptors See merge request tpo/core/arti!4005
| * | | | | tor-netdoc: Add bandwidth field to RouterDescClara Engler2026-05-262-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds the bandwidth field to the RouterDesc struct as it is found within the spec. The legacy parser will not support it, hence why we do default values there.
| * | | | | tor-netdoc: Add Bandwidth structClara Engler2026-05-262-0/+20
| | |/ / / | |/| | | | | | | | | | | | | | | | | | This commit adds the bandwidth struct for router descriptors which is present in the `bandwidth` item.
* | | | | Merge branch 'relay-clippy' into 'main'Nick Mathewson2026-05-272-1/+4
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Fix two unused warnings See merge request tpo/core/arti!4019
| * | | | | tor-chanmgr: fix `unused_imports` warningSteven Engler2026-05-271-1/+3
| | | | | |
| * | | | | arti-relay: fix `unused_variables` warningSteven Engler2026-05-271-0/+1
| | | | | |
* | | | | | Merge branch 'doc-digest-reorg' into 'main'Clara Engler2026-05-2712-67/+178
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | tor-netdoc: Implement encoding for referenced doc digest in rs entries See merge request tpo/core/arti!3989
| * | | | | tor-netdoc: Implement encoding for md rs digestIan Jackson2026-05-182-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is not tested yet. It will be tested when we add round-trip tests for votes.
| * | | | | tor-netdoc: Fix comment about from_unparsedIan Jackson2026-05-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | This doesn't parse the keyword, only the value.
| * | | | | tor-netdoc: Tidy doc_digest_parse2_m into doc_digest_item_mIan Jackson2026-05-182-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Rename it so that it doesn't mention parse2, because we're going to want to encode too. * Remove the indirection: rename the one in md.rs to be the name that's used in `with = `. (Previously, things were more complicated so the extra layer of indirection was helpful.)
| * | | | | tor-netdoc: rs referenced doc digests: Use FixedB64 (fmt)Ian Jackson2026-05-181-2/+1
| | | | | |
| * | | | | tor-netdoc: rs referenced doc digests: Use FixedB64Ian Jackson2026-05-187-43/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | FixedB64 is the right type for these, when they are present. This abolishes some ad-hoc boilerplate. Sadly we still need a bit of that for Reasons.
| * | | | | tor-netdoc: relay flags with: Use ns_type! rather than conditional importIan Jackson2026-05-181-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, this was't possible because derive-deftly wanted a string. But now it can take a type, and types can contain macro calls inside their generics etc. This makes the code much more local and direct.
| * | | | | tor-netdoc: Fix comments in rs variety filesIan Jackson2026-05-183-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | This is router *status* not router *descriptor*.
| * | | | | tor-netdoc: Fix NotPresent to use same Each valueIan Jackson2026-05-183-13/+93
| | | | | |
| * | | | | tor-netdoc: Document that parse2 vs encode multiplicity match req'tIan Jackson2026-05-183-4/+40
| | | | | |
* | | | | | Merge branch 'relay-destroy' into 'main'gabi-2502026-05-263-31/+161
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | proto: Add tests for DESTROY and TRUNCATE handling See merge request tpo/core/arti!4008
| * | | | | | proto: Remove TODOs about flushing pending dataGabriela Moldovan2026-05-262-8/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We decided the reactor is the wrong place to handle this. See discussion in #2490
| * | | | | | proto: Remove unused asyncGabriela Moldovan2026-05-201-3/+2
| | | | | | |
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 18:42:41 +0000