mirrors/arti.git/crates/tor-rpcbase, 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
Add a few "TODO RPC" notes2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-16T12:35:18Zurn:sha1:854b1507c95ca7edde01c545b0c7375912168944RPC: 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: Fill in documentation about invoke_special2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-14T18:45:48Zurn:sha1:69510aaa1750362d6df9d7e92b9b139d70071e17Tests for invoke_special2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-14T18:37:05Zurn:sha1:e3091d7ddd334e97dfd180d428cdfa1efdcb0350RPC: Fix types for DispatchTable::invoke_special2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-14T18:35:28Zurn:sha1:876d86bbdac363a810b020af06b74114189fad6c
Now that Method::Error exists, we can downcast Any to the actual
function's return type.
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: Allow invoker_ents to be marked as @special2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-14T17:55:45Zurn:sha1:035f624f3228aa95f8229df9014e5574d2bf2d5e
A @special invoker does not get an RPC entry.
Relax Serialize requirement on method outputs.2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-14T17:36:17Zurn:sha1:704b1ec7f9e92208b548ebf0e9ee50adfe9aa0d0
Now Methods can return anything; and only if their outputs are
Serialize will they implement RpcInvocable.
Split Invocable into RpcInvocable.2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-14T17:24:11Zurn:sha1:824e518c8b703c5575302a914aa17606ba3efb8a
RpcInvocable will only be implemented on types whose output
can be serialized.