mirrors/arti.git/crates/arti-rpcserver/src, branch arti-v1.2.7

extract tor_async_utils::oneshot into ::oneshot-fused-workaround

2024-08-28T14:27:46Z

Having this in the `tor-async-utils` crate prevents us from doing both of the following without introducing a circular dependency: * using it in `tor-rtmock` (which we currently do, particularly in tests). * using `tor-rtmock` to test things in `tor-async-utils`. We don't do this yet, but it is generally sensible to do so. In particular we want to move the `stream_peak` module there, which is currently tested with `tor-rtmock`. Moving this into its own crate avoids this circular dependency.

rpcserver: Fix a trivial doc typo.

2024-08-28T13:00:31Z

rpcserver: Use slotmap-careful instead of generational-arena.

2024-08-14T16:31:25Z

Unlike generational-arena, slotmap is maintained. Unlike slotmap, slotmap-careful should never be able to reuse the same key for two different objects. Closes #1282.

Merge branch 'rpc-connection-error' into 'main'

2024-08-13T15:13:39Z

rpcserver: use more sophisticated handling for ConnectionError. Closes #1517 See merge request tpo/core/arti!2335

rpcserver: use more sophisticated handling for ConnectionError.

2024-08-13T01:27:50Z

In general, we don't want to return a ConnectionError for a simple EOF condition; we only want to report an error when there's an actual failure. Also, it's a good idea to capture the actual error return conditions that we get from aynchronous_codecs, rather than throwing them away as we did before. Closes #1517.

Unstable RPC method to dump method information.

2024-08-13T00:27:03Z

Mark a struct as allowed-to-be-unused.

2024-07-28T21:48:35Z

(This will either become used later, or we will remove it; the TODO RPC will remind us.)

rpc: Rename the error codes for something like consistency.

2024-07-25T12:46:29Z

rpc: Remove RpcError data field and use Report

2024-07-25T12:46:29Z

Per discussion, this field isn't really specified in a way that lets us fill it sensibly at the moment. So for now, we're going to just omit it. Additionally, we said that we'd Report on our errors; this branch changes the implementation of RpcError to do that. Question: Will the blanket implementation for Into make it harder to re-add a Data field later on if we want to do so?

rpc: Refactor errors part 1: a new RpcMethod trait.

2024-07-25T12:43:30Z

It is no longer necessary to say, for every RPC method, that its error type is RpcError.