| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \
| | |
| | |
| | |
| | | |
Start a set of integration tests in python
See merge request tpo/core/arti!2515
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
(This is all on the theory that any formatting standard is better
than none.)
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Right now, we only support two things in the CLI:
overriding ARTI_RPC_TEST_DIR, and passing additional arguments to
arti_rpc_tests.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We use the `tomli_w` package to generate reasonable toml output,
instead of trying to use `str.format`.
Without this, there's not an easy way to tell string.Formatter
to convert Path('/abc/"def"') to `"abc/\"def\""`.
Something like this would be necessary even if we weren't using
Path, since the toml rules for sring encoding aren't the same as
produced by Python's repr(), which we were using before.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These tests are loosely modeled after stem's test suite for Tor and
the Tor control port. They're meant to exercise Arti, Arti RPC, and
the Arti RPC client library.
(For now, they exercise very little.)
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
arti-relay: Change it to a binary crate only
Closes #1674
See merge request tpo/core/arti!2525
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: David Goulet <[email protected]>
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: David Goulet <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The "pub" and "pub(crate)" visibility in a binary crate is essentially
the same except for the dead_code warning analysis which ignores "pub"
but will warn at "pub(crate)".
This should get fixed soon according to:
https://github.com/rust-lang/rust/issues/74970
However, for now, lets catch all this dead code :).
Part of #1674
Signed-off-by: David Goulet <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Simply, the lib.rs is renamed to relay.rs (containing TorRelay object)
so this crate can never be used as a library.
This is important because at the moment, we don't want to have a relay
stable API that can be used to embed relays in applications.
Closes #1674
Signed-off-by: David Goulet <[email protected]>
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
At the moment, it is an empty main() acting as a place holder for this
crate to become solely a binary crate.
Write up a basic README.md in order to explain the current state. Next
commit will remove the libary component by renaming lib.rs
Part of #1674
Signed-off-by: David Goulet <[email protected]>
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
tor-chanmgr: some cleanup and comments
See merge request tpo/core/arti!2523
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use memquota queue for channel->circuit RX data
Closes #1682
See merge request tpo/core/arti!2518
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes #1682.
(This involves some noise in the tests.)
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is neater and will make changing the type (in a moment) less
noisy.
|
| | | | |
| | | |
| | | |
| | | | |
We'll need this in a moment.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Use cargo features to reduce needless dependencies from arti-rpc-client-core
See merge request tpo/core/arti!2522
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is part of an effort to make arti-rpc-client-core (and future
similar tools) able to use our very-low-level crates
without depending on things they don't need.
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
This is part of an effort to make arti-rpc-client-core (and future
similar tools) able to use our very-low-level crates
without depending on things they don't need.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti-rpc-client-core: remove 'c_str_macro' dependency
See merge request tpo/core/arti!2524
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
Arti has a MSRV of rust 1.77 which supports C string literals, so
'c_str_macro' isn't needed.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
shadow CI: Add a couple of tests involving C Tor keystores
See merge request tpo/core/arti!2514
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This is needed to test C Tor keystore support in shadow.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
RPC spec: try to define a little more semantics and extensibility for `data`.
See merge request tpo/core/arti!2512
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is based on a suggestion from @diziet, but edited to say that:
- we will take this approach when possible, and that we're not making
a categorical promise.
- this approach only applies to stable fields.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
IIUC: Previously, `error.data` was meant to be the serialized error
object from Arti. As such, it was specified to be deliberately
unstable, and likely to change.
This didn't seem like such great idea, especially as we started to
come up with structured and stable data that we _did_ want to put in
`error.data`.
With this commit I'm taking a new approach to `error.data`.
Specifically:
* `error.data`, if present, is always an object.
* Unlike before, it can have multiple keys.
* The keys of `error.data` are always namespaced.
* There is a requirement that documentation exist for every key in
an`error.data` document, including the type, semantics, and
stability of its values.
There is also new "anticipated use of error.data" section
to clarify our plans:
* We plan to use error.data deliberately when it actually
serves a purpose.
* We don't plan to have an on-by-default serialization or Debug of
every Arti error. (If we wanted an optional one, there is a
short sketch of what it might look like.)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is *not* how we actually want the `data` field to behave!
But moving it as a separate commit will make it easier to see
what changes we do make.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-config: Fix indentation in doc comment.
See merge request tpo/core/arti!2520
|
| | | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
It looks like my previous attempt from !2516 didn't fix it.
This adds an extra space to fix the `doc_lazy_continuation` lint.
|
| |\ \ \ \ \
| |/ / / /
|/| | | /
| | |_|/
| |/| |
| | | |
| | | | |
memquota architecture documentation
Closes #1660
See merge request tpo/core/arti!2509
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2509#note_3089914
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
See
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2509#note_3089913
|
| | | | | |
|
| | | | | |
|