mirrors/arti.git/crates/tor-rpcbase/src/method.rs, branch arti-v1.4.5

tor-rpcbase: Removed dependency on `once_cell`

2025-06-15T02:11:18Z

- Replaced `once_cell::sync::Lazy` with `std::sync::LazyLock`. Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>

rpcbase: Make recognized namespace list optional.

2025-01-27T21:10:47Z

rpcbase: Move is_valid_rpc_identifier to crate root.

2025-01-27T21:10:47Z

rpc: Rename InvalidMethodName to InvalidRpcIdentifier.

2025-01-27T18:33:33Z

We're about to use this error type for other things too.

Remove RPC TODO about bypass_method_dispatch method.

2025-01-27T18:27:38Z

There was formally a redundant method of this name, which could get out-of-sync with invoke_without_dispatch. But now that method is gone, and this TODO is wrong.

rpc: Make cancel requests uncancellable.

2025-01-23T00:39:58Z

The current cancel code is prone to deadlock, so the easiest way to solve it appears to be making cancel requests themselves uncancellable. I've included a test to verify the behavior; previously, this test caused a deadlock.

rpc: Simplify method-dispatch-bypass logic a bit

2024-10-24T01:35:05Z

This commit removes the separate function for asking whether to bypass the dispatch code. Instead, it gives the "invoke with bypass" function an error to return when no dispatch is warranted, and moves the whole responsibility for method dispatch or non-dispatch back into tor-rpcbase. I had to add an ObjectId argument to `invoke_rpc_method` to make this work, but that's probably a good thing. Additionally, this commit tweaks the derive-deftly macro to prevent you from asking for dispatch bypass on special methods, where it isn't implemented (and doesn't really make sense).

rpc: Add a mechanism for method that bypass regular dispatch

2024-10-24T01:35:05Z

I'm about to use this for rpc:release, which is special because it doesn't actually look at the type of the object that it's invoked on. Later it might be useful for manipulating weakrefs, cloning referenes, detecting reference equality, etc.

rpcbase: Facility for looking up RPC method information

2024-08-13T00:19:20Z

We'll need this to refer to the names of RPC methods as visible to the caller, and to cross-reference them with their related types.

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.