| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
| | | |
| | | |
| | | | |
(Found while writing a test.)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In older versions of the rpc spec, this field held a serialized
version of the Arti error object. That's no longer the design: now
it provides a way for specific errors to include extra, specified,
machine-readable data. For more information see the section
"Errors" in rpc-meta-draft.md
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These are not regular ErrorKinds, since they can never occur in an
error that's meant to be returned from a Rust API like
`arti-client`. Instead, they only exist for errors returned from
RpcError.
(I can't find the place where we discussed this previously, but the
rationale is that if an ErrorKind never makes sense in response to
something that the user does from Rust, we should never have that be
an ErrorKind. The fact that the removed kinds do not actually
appear outside the RPC system suggests that this is reasonable.)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I'm about to remove HasKind from InvokeError, which would otherwise
break this code.
These errors are all in fact internal errors, since in this context
they can only stem from incorrectly formed calls to
`invoke_special_method`.
|
| | | | |
| | | |
| | | |
| | | | |
In some cases, the tor_error::ErrorKind names were nicer.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We'll use this to make RpcErrors directly, without having to go
through an error that implements HasKind.
Later, we'll add the ability to set the `data` fields on an RpcError.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This change will let us start removing the not-entirely-logical
`Rpc.*` variants from tor_error::ErrorKind.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This is about to be a public competitor with tor_error::ErrorKind.
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
memquota: suppress clippy::single_match warning.
See merge request tpo/core/arti!2555
|
| |/ /
| |
| |
| |
| | |
"Suppress" rather than "fix": this pattern is intentional, and
makes it clear that we're doing an exhaustive match.
|
| |\ \
| | |
| | |
| | |
| | | |
tor-key-forge: Minor cleanups and reformatting
See merge request tpo/core/arti!2552
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
`KeypairData` is already in scope, so there's no need to fully-qualify
it.
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Disable a lot of dead code warnings and add a default-runtime feature in arti
See merge request tpo/core/arti!2551
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now one can do a minimal build with
cargo build -p arti --no-default-features --features=default-runtime
rather than needing to specify tokio,native-tls.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now
cargo check --workspace --no-default-features --all-targets
cargo build -p arti --no-default-features --features=memquota,tokio,native-tls
are both clean.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-chanmgr: update comments about selecting pending channels
See merge request tpo/core/arti!2544
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-chanmgr: refactored to remove `with_channels` and added `PendingChannelHandle`
See merge request tpo/core/arti!2538
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This handle contains all of the details required to remove or replace a
pending channel entry from the channel map.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
These methods on `MgrState` acquire a lock, and it's easy for calling
code to also try to acquire the same lock within the closure, causing a
deadlock. It's better to not expose these methods.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Best reviewed with the '-w' flag to hide whitespace changes.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This moves most of the channel map logic from
`AbstractChanMgr::choose_action` to `MgrState::request_channel`.
This is working towards being able to remove
`MgrState::with_channels{,_and_params}`.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
rtcompat: Fix android compilation in `general`
See merge request tpo/core/arti!2553
|
| | | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously I had assumed that `std::os::linux` also existed on
android, based on the documentation of
`std::os::linux::net::SocketAddrExt`. That is not, however, true.
This should fix the `check-targets` CI job.
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
RPC: Sketch for how connect strings work
See merge request tpo/core/arti!2439
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
This is based on conversations with Diziet,
and is a followup from arti!2388 and arti!2429.
|