| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| | |
1. When we are told to `extend_with`, we should obey that directive
even if we have a sub_builder etc.
2. Provide an `extend_with_replace` function for the common case
where we want to just replace one object with another.
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
| |
`clippy::collapsible_if` started triggering after bumping the MSRV to
1.88.
Since this triggers from a lot of places, and since there even are a
couple of instances where we explicitly allow `clippy::collapsible_ifs`,
I've opened #2342 for deciding what to do about it.
|
| |
|
|
|
|
|
| |
As agreed at our last team meeting.
See
https://gitlab.torproject.org/tpo/core/arti/#minimum-supported-rust-version
|
| |\
| |
| |
| |
| | |
Allow to set paths in CLI arguments
See merge request tpo/core/arti!3556
|
| | |
| |
| |
| | |
The set of allowable characters now includes colon, dot, slash, and backslash. This makes it a bit more convenient to pass in paths.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Done via:
```
for crate in $(./maint/list-crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.39.0
done
```
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
arti: Remove `proxy.socks_port` and `proxy.dns_port`
Closes #2300
See merge request tpo/core/arti!3622
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
I'm undecided whether we want to keep `resolve_alternative_specs`
around, but it seems possible/likely that we'll want it in the future,
so I think we can keep it.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
fix(minver): Update paste dependency to be minver compatible
See merge request tpo/core/arti!3610
|
| | | | |
|
| |/ /
| |
| |
| | |
This adds the lint to all our crates.
|
| | |
| |
| |
| |
| | |
Fix the conflict in tor-netdoc/semver.md by hand, including the new
entries already landed since v1.9.0.
|
| |/
|
|
|
|
|
|
|
| |
Done using the following:
```bash
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.38.0
done
```
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
These are a nicer syntax than using port "0" explicitly.
|
| |
|
|
| |
Nothing actually uses it any more, which is good.
|
| |
|
|
|
| |
Have the part of them that does the "no multiple addresses" work
be common, so that we can simplify how they actually behave.
|
| | |
|
| |
|
|
| |
This reverts commit c7c8eb5a03439ce31319389183e64cb0db539fc9.
|
| |
|
|
|
|
|
|
| |
This template is meant to replace most of our use of derive_builder
for configuration objects. Where possible and reasonable, it
delegates to existing macros, and automatically infers what special
patterns we use for individual types. In other cases, it uses
compile-time errors to inform the caller about pattern violations.
|
| |
|
|
|
|
|
|
| |
This trait will be implemented by every type that our
derive_deftly(TorConfig) template generates. It will, among other
things, help us figure out the Builder type for a given config type
in cases where string-pasting magic is intractable, or where we
want to use assert_not_impl to double-check the attributes.
|
| |
|
|
|
| |
The derive-deftly TorConfig template will use these as appropriate
for the inputs to setter functions, based on field types.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
If we don't do this, then any attempt to use it from a derive-deftly
template will cause a warning about referring to it as
$crate::macroname.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
derive_deftly wants to expand types before passing them to
macro_rules macros, which is quite reasonable. But map_builder
wants its input collection type to be an `ident`, not a `path`.
(And macro_rules doesn't accept `path` before a `<`.)
To fix this, we're providing an alternative syntax for map_builder,
where the inputs are the map type and the builder map type.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
We were only using it for Default, and it is easier to implement
Default by hand than it is to keep this particular layer in our
leaning tower of macros.
|
| |
|
|
|
|
|
|
|
| |
This has:
* Fixes to hygiene spans from the new modules feature, needed for
my WIP netdoc encoder derive.
* A substantially richer `${error }` construct.
|
| |\
| |
| |
| |
| | |
tor-config: Refactor `Listen` to make usable for arti-relay
See merge request tpo/core/arti!3469
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Assumes that 0.37.0 will be the next version number.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
There was no reason for this to be public.
|
| | |
| |
| |
| | |
This does a little extra cloning, but I think is easier to read.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For example the old message would look like:
```text
target/debug/arti: error: read configuration: Config contents not as
expected: Couldn't load configuration: data did not match any variant of
untagged enum ListenSerde for key "default.proxy.socks_listen" in
command line
```
The new message looks like:
```text
target/debug/arti: error: read configuration: Config contents not as
expected: Couldn't load configuration: value was not a bool, `u16`
integer, string, or list of integers/strings for key
"default.proxy.socks_listen" in command line
```
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.37.0
done
|
