| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This lets us skip fields which have the default values.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
All these types already have parsing derives.
The encoding isn't quite right yet. It's legal, but doesn't match C
Tor as well as we'd like.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Create dirauth crates (empty)
See merge request tpo/core/arti!4122
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Let's start this now.
|
| | | | | | | |
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
We already seem to use "network-programming", which kind of fits.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Use roundtrip_netstatus, which does nearly all of the work for us.
But for it to round-trip, we must do a bunch of fudging.
This replaces the old parse2 vote test case (which used the poc type).
The test case has some adjustments to cope with missing fields. Move
the TODOs for those fields to the test case, so that they're on lines
that will be deleted when the fields are implemented.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Right now we're working on votes, but the same issue arises in
consensuses; we just haven't noticed yet because the testdata2
consensus doesn't have an SRV.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In the future (not quite yet in this branch), there will be tests that
want to use roundtrip_netstatus for other test files.
We'll want to be able to reuse the per-document-specific munging. So
make that into a trait. And document roundtrip_netstatus.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This will let us do more exciting munging more clearly.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The vote test files are for the next consensus interval, so we need to
verify them at a slightly future time.
|
| | | | | | |
|
| |/ / / / |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti: Rewrite hand-written tests using `trycmd`
See merge request tpo/core/arti!4126
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now that these test more than just the help output, we need to gate them
behind the `onion-service-service` feature: the tests involve some C Tor
keystores, and require at least one onion service to be configured,
because onion services (and clients) are the only thing these keystores
are used for.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We now have `trycmd` tests that cover most cases, so I am removing this
module. The reason this was introduced in the first place is in the
module level docs
```rust
//! The `assert_cmd` crate is used here instead of the preferred `trycmd` (see
//! [`README`](../README.md)) because the output of `keys list` is not deterministic across
//! different machines. The design choices of some components are workarounds for this limitation.
```
But this is no longer an issue now that the `keys list` output is
sorted.
Ideally, all tests would be written this way (we have a few more modules
in `cli_tests` that we should probably port to `trycmd` sometime).
Note: some of the tests I'm removing here don't have a `trycmd`
counterpart in `arti/tests/testcases/keys`. In my opinion, this is
perfectly fine, because the old tests were unnecessarily testing all the
possible configurations involving 1-2 keystores (one arti, and one C
Tor): it is not the responsibility of the CLI tests to cover all these
permutations (they should be tested in `tor-keymgr`).
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a `trycmd`-based replacement for the
`list_unregistered_keystore_fails()` test, which will be removed soon.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This un-ignores some of the output snippets from the `doc/keys.md` file,
so that our `trycmd` test runner will actually run them. This will force
us to keep the snippet in sync with the code.
This involved adding some extra config for the test C Tor keystore,
and tweaking the output to match what the commands actually print out.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will make the output deterministic and enable us to write some
`trycmd` tests in the form of markdown output snippets.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Replaces a push by using the chain!() macro from itertools.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
() implements encodable which we will derive soon.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit implements NetdocEncodableFields for AddrPolicy in a
non-trivial fashion. A unit test will be added in a moment.
|
| | |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
This commit makes some policy related constructor functions constant, so
we can use them in const expressions, which will be required for the
next commit.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Bump MSRV to 1.91
See merge request tpo/core/arti!4105
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit bumps the MSRV to 1.91 which was released on 2025-10-30.
The Cargo.toml files were updated as follows:
```sh
git ls-files | \
grep ".*Cargo\.toml$" | \
xargs sed -i '' 's/^rust-version = "1\.89"$/rust-version = "1\.91"/g'
```
The following files were updated manually:
```
modified: .gitlab-ci.yml
modified: README.md
modified: flake.nix
modified: maint/docker-android/Dockerfile
```
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-netdoc: derives: allow handling deprecated fields
See merge request tpo/core/arti!4118
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
We must generally set such a field to the default.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This makes it possible to derive from a struct with deprecated fields,
without triggering the warning.
This doesn't yet treat encoding as yet, because the only deprecated
field I encountered was `skip` which means the derived encoder never
mentions it.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fix string_slice exceptions outside of netdoc
See merge request tpo/core/arti!4092
|
| | | | | | | | |
|
| | | | | | | | |
|