Missing RPC methods cause admin UI errors (redis.select, redis.keys, etc.) #9

New issue

Closed

opened 2026-02-24 14:19:02 +00:00 by mahmoud · 1 comment

mahmoud commented

2026-02-24 14:19:02 +00:00

Owner

Description

After the refactor to a pure-proxy _http crate, the admin UI calls several
RPC methods that the _openrpc backend never implemented, causing:

[-32601] Method not found: redis.select

Methods missing from hero_redis_openrpc dispatcher:

redis.select — used by selectDatabase() and flushDatabase()
redis.keys — used by the key browser
redis.get — used to view key values (needs type detection)
redis.del — used to delete keys
redis.database_create — used by the create-DB form and navbar

Additionally, the flushDatabase flow calls select→exec(FLUSHDB)→select(0)
as three separate HTTP requests. Since each request creates a fresh
stateless session, the SELECT does not persist and FLUSHDB always runs
on DB 0 instead of the target database.

### Description After the refactor to a pure-proxy _http crate, the admin UI calls several RPC methods that the _openrpc backend never implemented, causing: [-32601] Method not found: redis.select Methods missing from hero_redis_openrpc dispatcher: - redis.select — used by selectDatabase() and flushDatabase() - redis.keys — used by the key browser - redis.get — used to view key values (needs type detection) - redis.del — used to delete keys - redis.database_create — used by the create-DB form and navbar Additionally, the flushDatabase flow calls select→exec(FLUSHDB)→select(0) as three separate HTTP requests. Since each request creates a fresh stateless session, the SELECT does not persist and FLUSHDB always runs on DB 0 instead of the target database.