You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
redis 8.1.0's ConnectionPool.__init__ now injects its own himport_registry into connection_kwargs, and Redis.__init__ doesn't accept it. Since this probe runs during connection setup, every query fails before anything is sent.
#235 was the same thing with a different key — path instead of himport_registry, same function, same line, same unexpected keyword argument. It was fixed by special-casing that one key:
I patched this locally on falkordb 1.6.2 + redis 8.1.0 and async works again (RETURN 1 → [[1]]). Filtering by signature also covers the path case, so the existing special-case could go.
The sync client already does something similar in cluster.py — it pulls fields out by name rather than forwarding everything, which is why it never broke.
Also worth noting
redis>=7.1.0 has no upper bound, so this reaches users the moment redis publishes. Might be worth a cap until the fix ships.
Bump redis from 7.4.0 to 8.1.0 #258 (Bump redis 7.4.0 → 8.1.0) has been failing on Python 3.10–3.14 since 2026-07-30 with this exact TypeError. The fix above should make it green.
Versions
falkordb 1.6.2, redis 8.1.0 (8.0.1 works), Python 3.11 / 3.12, macOS + Linux CI
A clean
pip install falkordbtoday pulls redis 8.1.0, and the async client can't run anything:The sync client is fine, and redis 8.0.1 is fine — it's only async + redis >= 8.1.0.
What's happening
Is_Cluster()infalkordb/asyncio/cluster.pyforwards the wholeconnection_kwargsdict into a sync client:redis 8.1.0's
ConnectionPool.__init__now injects its ownhimport_registryintoconnection_kwargs, andRedis.__init__doesn't accept it. Since this probe runs during connection setup, every query fails before anything is sent.This is #235 again
#235 was the same thing with a different key —
pathinstead ofhimport_registry, same function, same line, sameunexpected keyword argument. It was fixed by special-casing that one key:redis shipped 8.1.0 eleven days later and it broke again. Any future internal addition on redis's side will do the same.
Suggested fix
Pass only what
Redis.__init__actually accepts:I patched this locally on falkordb 1.6.2 + redis 8.1.0 and async works again (
RETURN 1→[[1]]). Filtering by signature also covers thepathcase, so the existing special-case could go.The sync client already does something similar in
cluster.py— it pulls fields out by name rather than forwarding everything, which is why it never broke.Also worth noting
redis>=7.1.0has no upper bound, so this reaches users the moment redis publishes. Might be worth a cap until the fix ships.TypeError. The fix above should make it green.Versions
falkordb 1.6.2, redis 8.1.0 (8.0.1 works), Python 3.11 / 3.12, macOS + Linux CI