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

Revert "rpc: Suppress a clippy false positive that appears with current beta"

2026-05-04T14:17:54Z

This reverts commit 9447e48d0c698d51c75706d5efedcd6142c82f2a, which told Clippy to ignore a warning that (I think) no longer occurs. (Clippy was complaining that we were _naming_ a function in a const-context that wasn't const-stable at our MSRV. But it's fine to _name_ a non-const function in that case: we just can't _call_ it.) See https://github.com/rust-lang/rust-clippy/issues/15792 for more info on the clippy bug. AFAICT the warning no longer appears with current beta, nightly, or stable versions.

rpc: Suppress a clippy false positive that appears with current beta

2025-09-30T10:09:46Z

Switch Cargo.toml files to edition 2024.

2025-08-07T15:28:36Z

First, run ``` git grep -l "^edition =" | xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;' ``` Second, manually verify that all Cargo.toml files have changed, and nothing else has changed. Third, run cargo fmt again.

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).