mirrors/arti.git/crates/arti-rpcserver, branch arti-v1.2.4mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.42024-06-05T15:06:54ZBump all the unstable tor- and arti- crates to 0.19.2024-06-05T15:06:54ZGabriela Moldovangabi@torproject.org2024-06-05T15:06:54Zurn:sha1:7a11638841eeabd2b5ebfe307541926c29cbfe77
The unstable crates are:
- tor-error
- tor-config
- tor-units
- tor-geoip
- tor-rtcompat
- tor-rtmock
- tor-log-ratelim
- tor-rpcbase
- tor-memquota
- tor-llcrypto
- tor-protover
- tor-bytes
- tor-hscrypto
- tor-socksproto
- tor-checkable
- tor-cert
- tor-linkspec
- tor-cell
- tor-proto
- tor-netdoc
- tor-consdiff
- tor-netdir
- tor-relay-selection
- tor-persist
- tor-chanmgr
- tor-ptmgr
- tor-guardmgr
- tor-circmgr
- tor-dirclient
- tor-dirmgr
- tor-keymgr
- tor-hsclient
- tor-hsservice
- tor-hsrproxy
- arti-client
- arti-rpcserver
- arti-hyper
- tor-basic-utils
- tor-async-utils
Done using
```
for p in "${unstable[@]}"; do cargo set-version -p $p 0.19; done
```
where `unstable` contains the list above
arti-rpcserver: Reformat Cargo.toml.2024-06-05T11:47:47ZGabriela Moldovangabi@torproject.org2024-06-05T11:47:47Zurn:sha1:f518076ce0e4bbdb20cb9b7f6aca951f17022569Run fixup-features in preparation for release.2024-06-05T11:47:29ZGabriela Moldovangabi@torproject.org2024-06-05T11:47:29Zurn:sha1:fabc5573600f290e4dd20afc9085afe6dfe40c8eRPC: Expose dispatch table from Context2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-14T18:52:36Zurn:sha1:533b34a55b268ec73ac032dd8e3d360f2d43b985
We need to do this so that we can actually invoke RPC functions
from one another.
RPC: Require an Error type in methods.2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-14T18:19:30Zurn:sha1:98765e5a4cdf70356db38d324b0896d2b6f83c2f
This is needed so that we can cast special methods' return types
properly.
I wish I could make this optional, but Rust doesn't allow
defaulting an associated type.
rpc: Move typetag onto subtrait of DynMethod2024-05-16T12:40:04ZNick Mathewsonnickm@torproject.org2024-05-14T15:21:02Zurn:sha1:0e8608ba76f61a401040c8f762b99e5f3965d8e8
This will allow us to create dispatchable methods that are only
invoked from inside the arti code, and are not themselves
serializable.
RPC: Give error from RpcMgr::new if method name is sufficiently bad.2024-05-14T13:49:44ZNick Mathewsonnickm@torproject.org2024-05-14T13:46:02Zurn:sha1:9f50a947a9859535c02aa117fe1cd4fea4fff09b
(We don't give an error about unrecognized namespaces (for now),
since we have no way to opt in to them.)
RPC: Enforce method name format.2024-05-14T13:39:47ZNick Mathewsonnickm@torproject.org2024-05-14T13:35:19Zurn:sha1:8da4b96991c01ff16bd1194bca77d9bedf0bb9fa
We need to do this carefully, since we want our system to be
extensible with new namespaces.
First, when we are constructing an RpcMgr, we _warn_ about any
method names that are misformed.
Second, we add a test in the `arti` crate to fail if any method
names are invalid. This will only catch method names in crates that
`arti` depends on.
RPC: Use RPC method names in a consistent format.2024-05-14T13:33:36ZNick Mathewsonnickm@torproject.org2024-05-14T13:33:36Zurn:sha1:24efb91741ba1acc139207ee805d385240f8c393
Specifically, we want a single colon, and we want our
method names to be in snake_case.
RPC: Require DynClone for ClientConnectionError.2024-05-14T12:04:03ZNick Mathewsonnickm@torproject.org2024-05-13T15:19:21Zurn:sha1:cb9ae08a5fe9e035b5d72562d05e33d16ca821d0