| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
This gets rid of a spurious warning on nightly about the use of dbg!
|
| | |
|
| | |
|
| |
|
|
| |
We're going to reuse this.
|
| |
|
|
|
|
| |
The error message from `#[serde(untagged)]` would otherwise start to
appear when we try to deserialise unsupported PT configurations, when
compiled with bridge but not PT support.
|
| |
|
|
|
|
|
|
| |
From Unsupported. Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/889#note_2856873
This was added in this MR.
Also add the missing semver note.
|
| |
|
|
|
|
|
|
|
| |
From Unsupported. Following one of the suggestions here
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/889#note_2856873
This was added in 2c3711614908d0c9cf1663b20b67a3fc233301f4 which was
not yet in a release so this isn't a semver break. I have added
the semver note that was omitted in that MR.
|
| |
|
|
| |
Fixes #612
|
| |
|
|
| |
And use it in bridge configuration parsing.
|
| | |
|
| |
|
|
| |
By changing MultilineListBuilder.
|
| |
|
|
|
| |
This trait can have this ludicrously long name because no-one needs to
import it.
|
| |
|
|
|
| |
It looks like, despite a few false starts, they've got this warning
right; there weren't any false positives.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Apparently cargo fmt doesn't like these, which my perl rune didn't
delete.
This commit is precisely the result of `cargo fmt`.
|
| |
|
|
|
|
|
|
| |
The feature we want is `#[doc = include_str!("README.md")]`, which is
stable since 1.54 and our MSRV is now 1.56.
This commit is precisely the result of the following Perl rune:
perl -i~ -0777 -pe 's{(^//!(?!.*\@\@).*\n)+}{#![doc = include_str!("../README.md")]\n}m' crates/*/src/lib.rs
|
| | |
|
| |
|
|
| |
This is what we'll use to parse the `bridges.bridges` config key.
|
| | |
|
| |
|
|
|
| |
We're going to use this for the config item `bridges.enabled`,
but it seems general enough that it ought to go here.
|
| |
|
|
|
|
|
|
| |
We're going to want something that has the standard list builder
methods at the Rust API, but which has different serialisation.
Sadly the implementation is annoying, because macro_rules makes it
hard to parse a nice input syntax.
|
| |
|
|
|
|
|
| |
This lint exists for perf reasons, and this is rarely relevant in
tests.
Using double quoted str is generally cognitively less burdensome.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
`${PROGRAM_DIR}` expands to the equivalent of
`std::env::current_exe().parent()`, with appropriate unwrapping and
conversions.
It is expected to be useful for finding the locations of pluggable
transports in some kinds of bundles.
Closes #586.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Remove `anyhow` from `tor-config` crate
See merge request tpo/core/arti!707
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
And linkify it.
|
| |/ |
|
| |\
| |
| |
| |
| | |
tor-config: tests: Apply standard lint block in sources.rs
See merge request tpo/core/arti!694
|
| | |
| |
| |
| | |
Fixes a spurious clippy warning on nightly, about a dbg!
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Whereas previously we would say:
```
target/debug/arti: error: invalid escape character in string: `Z` at line 9 column 14 in ../../.config/arti/arti.toml
```
we now say:
```
target/debug/arti: error: invalid escape character in string: `Z` at line 9 column 14 in ../../.config/arti/arti.toml (If you wanted to include a literal \ character, you need to escape it by writing two in a row: \\)
```
The implementation is a bit of a hack, I'm afraid, but I don't think
it's all that bad.
Closes #549.
|
| | |
| |
| |
| |
| | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/602#note_2830847
|
| | |
| |
| |
| |
| | |
Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/602#note_2830848
|
| | |
| |
| |
| |
| | |
Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/602#note_2830766
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This will allow us to handle new kinds of warnigns etc.
|
| | |
| |
| |
| | |
We're going to want the to use the same type for deprecated keys.
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
FoundConfigFile existed to hide something that ConfigurationSource now
exposes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/682#note_2830860
And subsequent IRC discussion.
Having done the work as per review comments, I don't much like the
result. It's quite un-ergonomiuc. If we can't have fs autodetection,
I think syntactic autodetection within sources.rs would be nearly as
nice.
However, I seem to be outvoted. At least the externally visible
functionality (of an arti binary, say) is reasonably ergonomic.
|
| | |
|
| |
|
|
| |
I think this ought to be exhaustive.
|
| |
|
|
| |
Fixes #474 aka #271
|
| | |
|