mirrors/arti.git/crates/arti-rpc-client-core/src/conn.rs, branch arti-v1.2.8mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.82024-09-10T18:25:43Zrpclib: Rename connect.rs to stream.rs2024-09-10T18:25:43ZNick Mathewsonnickm@torproject.org2024-09-10T18:25:43Zurn:sha1:10728f57bcbb1b42cc3efec5ac07b507d916c1a2
(This is about DataStreams, so we should make it less confusing.
This commit is _just_ about the file renaming, with no associated
function renaming.)
rpclib: FFI for opening data streams.2024-09-09T14:52:56ZNick Mathewsonnickm@torproject.org2024-08-26T15:31:18Zurn:sha1:8fd335e5ae7ad761efe3030e33b7004ec70fc2ff
There's a blocking TODO here about exposing socks error codes that
I still need to solve.
rpclib: Support opening a data stream.2024-09-09T14:52:56ZNick Mathewsonnickm@torproject.org2024-08-23T02:08:30Zurn:sha1:035aaa8fabf8489167e5a60bbe84fd0c4acccfe6
Requires #1523.
Implements #1524.
Fix typos2024-09-03T08:09:02ZDimitris Apostoloudimitris.apostolou@icloud.com2024-09-03T08:09:02Zurn:sha1:676f913463b7d84f34dd6101b99d03ef79cf57adrpclib, ffi: Allow simultaneous calls to `arti_rpc_handle_wait()`2024-08-27T13:45:12ZNick Mathewsonnickm@torproject.org2024-08-22T15:21:48Zurn:sha1:76e6a24759b5fc1a04b53077acb19afb82c8df88
Its underlying function previously took `&mut RpcHandle`,
which was an accident waiting to happen. Now it takes `&RpcHandle`
and includes a Mutex to prevent multiple threads from waiting for
updates on the same request ID at once.
As an alternative, we *could* try to update connimpl::Receiver to
allow multiple simultaneous listeners on the same request ID.
But that would (I think) require a lot more bookkeeping, and thus
would be a bit more error-prone.
Closes #1532.
rpclib: Allow ConnectionClosed in arti_socket_closed test2024-08-21T12:47:55ZNick Mathewsonnickm@torproject.org2024-08-15T17:07:10Zurn:sha1:d866fd0b2da368a8c02f060630a90b27c9770ce9
This test is supposed to check the case where we launch a bunch
of requests but the socket is dropped before we get a response.
Different operating systems handle 'drop' a bit differently,
and schedule threads differently, so we shouldn't be surprised
at slightly different errors here.
In particular, OSX is more prone to deliver the close as a proper
"close" rather than an EPIPE or such, which previously broke
this test.
Closes #1510.
ffi: Add support for request handles2024-08-12T18:35:09ZNick Mathewsonnickm@torproject.org2024-08-06T15:57:54Zurn:sha1:2364c6dc6d2fd16f08641a1fed2cbc970005dc66
This API allows the caller to launch a request and then watch for
updates on it.
rpclib: Unify error type for ValidatedRequest failure.2024-08-07T12:21:28ZNick Mathewsonnickm@torproject.org2024-08-06T13:05:02Zurn:sha1:5756400a33f1a4e35d676aaa90bad69ac34aaab2rpclib: Refactor request canonicalization2024-08-07T12:21:28ZNick Mathewsonnickm@torproject.org2024-08-06T12:50:24Zurn:sha1:2eaa2dc0c902411b83365e9e2f11da268f98a8fd
This lets us make a couple of types module-private,
and prepares the way for using the serde_json::Value trick on
requests too.
Merge branch 'rpc-reencoding' into 'main'2024-08-05T18:07:58ZNick Mathewsonnickm@torproject.org2024-08-05T18:07:58Zurn:sha1:32d95e1c99843f598afbfb85e30885d6bc2182fe
rpc-client-core: Always re-encode requests and responses, and preserve unrecognized struct fields.
Closes #1491
See merge request tpo/core/arti!2312