| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
| | | |
| | | |
| | | |
| | | | |
From running add_warning, with manual picking of the right
hunks/lines.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
add_warning can now add allows. This one was agreed in some other MR
for one crate. Allow it everywhere.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
These were in some crates, but not all. Put them in add_warning
where they will propagate everywhere.
|
| | | | |
| | | |
| | | |
| | | | |
These need to survive.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We don't process the in-script lint block, just paste it in, now.
This is less complicated.
This reverts/replaces
"maint/add_warnings: Make it add the markers for its future self"
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was the result of:
maint/add_warning crates/*/src/{lib,main}.rs
and then manually curating the results.
|
| | | | |
| | | |
| | | |
| | | | |
We'll run this in a moment. Then we'll revert it.
|
| | | | |
| | | |
| | | |
| | | | |
We are going to make lints the same for every crate.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The crates we have aren't consistent. But changing this means the
deltas resulting from the script are smaller.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This puts the actually-used lint list at the top.
No functional change.
|
| | | |/
| |/|
| | |
| | | |
This is ridiculous.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
proto: Only ready a DataStream if CONNECTED was succesfully received
See merge request tpo/core/arti!556
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: David Goulet <[email protected]>
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti config: Check that example config is exhaustive
See merge request tpo/core/arti!546
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/546#note_2808892
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This is the final piece of #457.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This allows us to add the proper default example to the arti example
config file.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now the validated configuration will never be `Some(0)`, even if that
is what was written in the config file. The arti CLI parser can still
produce this, so we don't touch the code that actually uses this.
(Without the canonicalisation the default builder produces `None` for
the `dns_port`, but the example would produce `Some(0)`, which is
semantically identical but fails the test.)
See https://gitlab.torproject.org/tpo/core/arti/-/issues/488 for some
background.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Canonicalise the `logging.journald` setting in the validated
configuration. Now it will never be `Some("")`, even if that is what
was written in the config file.
This allows us to write `journald = ""` in the example configuration.
(Without the canonicalisation the default builder produces `None` and
the example would produce `Some("")`, which are semantically identical
but fail the test.)
See https://gitlab.torproject.org/tpo/core/arti/-/issues/488 for some
background.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These weren't previously discussed. It's not practical or useful to
show the actual default values here.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Found by my forthcoming test.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This makes the config default parser see just "[ ]", an empty list,
which is indeed the default.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These violate our rule that *built* structs ought not to be desr.
But this is just in a test.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
That this remained was an oversight.
|
| | | | | | |
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
This was upposed to be one day, I presume!
Also complete a truncated sentence in the docs.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-dirclient: Require that self.digests is nonempty
See merge request tpo/core/arti!553
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti-config: Change description of tombstone crate
See merge request tpo/core/arti!558
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I was looking to see if we could delete this altogether but I
discovered that on lib.rs the description does not say it's a removed
crate, in the summaries.
Fix this.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Add a few coverage-based tests to tor-config.
See merge request tpo/core/arti!540
|
| | | | |
| | | |
| | | |
| | | | |
There's nothing major here, but it does fill in a few gaps.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Revert "Remove dbg!()s in tor-config"
See merge request tpo/core/arti!552
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was done because Nightly Rust complained about these, despite
them all being in tests. That is now fixed upstream:
https://github.com/rust-lang/rust-clippy/issues/8758
https://github.com/rust-lang/rust-clippy/pull/8838
This reverts commit 9d26a91886990b08dc5b6033c290d417489c61fc.
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
Fix minor issues found while publishing crates for Arti 0.4.0
See merge request tpo/core/arti!547
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Cargo publish (and probably nobody else!) builds this crate with no
features enabled. When you do that, you get a warning about an
unused `use std::io`.
Fixing that.
|
| | | | |
| | | |
| | | |
| | | | |
There is no "tor" category; crates.io warned about this.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
fs-mistrust: add getegid() to getgrouplist() output.
Closes #487
See merge request tpo/core/arti!548
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes a unit test failure in weird environments (like some
containers) where the current effective GID is not included in the
list of current groups.
Closes #487.
Bug reported by @sjm217.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
add unit tests for ArtiConfig public functions
See merge request tpo/core/arti!551
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
this change adds some simple tests for the ArtiConfig public getter
functions to help expand coverage in this crate.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Lexically sort Cargo.toml dependencies
Closes #490
See merge request tpo/core/arti!549
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Utilize cargo-sort: https://github.com/DevinR528/cargo-sort
Signed-off-by: Orhun Parmaksız <[email protected]>
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Update semver_status.md with new procedure.
See merge request tpo/core/arti!545
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now (per discussion on #471) we use one file per crate.
I've tried to be more explicit about the format to use, and what to
add when.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
fs-mistrust: Document problems with non-UTF8 OsString in toml
See merge request tpo/core/arti!538
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It turns out that the `toml` crate can't handle OsString, since
`toml` doesn't support serialize_newtype_variant, and the `serde`
crate tries to serialize OsString using that method.
In this commit we document that limitation, and test that we can at
least round-trip through json.
Found by inspecting test coverage.
|