Files
zeekay f47fd29d53 revert the KV client and psrpc swaps here — the build needs upstream types
livekit cannot use github.com/hanzokv/go, for a structural reason rather than a
stylistic one: the client type flows through two upstream libraries we do not
fork. livekit/protocol/redis.GetRedisClient PRODUCES a
github.com/redis/go-redis/v9.UniversalClient and livekit/psrpc CONSUMES one, so
substituting the client in the middle fails to type-check at both seams:

  cannot use redis2.GetRedisClient(&conf.Redis) (go-redis UniversalClient)
    as kv.UniversalClient in return statement
  cannot use rc (kv.UniversalClient)
    as go-redis UniversalClient in argument to psrpc.NewRedisMessageBus

Forking psrpc made it worse rather than better: livekit/protocol/rpc demands
livekit/psrpc's OWN types, so pointing at hanzoai/psrpc broke pkg/agent, which
had compiled. Verified by building pkg/agent at the commit before the fork
(compiles) and after (2 type errors) with a working SDKROOT — an earlier check
of mine reported "compiles in both" and was simply wrong.

So this repo keeps upstream go-redis and upstream psrpc (v0.7.1). That is the
honest consequence of livekit/protocol being unforkable: you cannot substitute a
client library inside a module whose upstream dependencies both produce and
consume that library's types.

What stays, because it is correct and independent: the module path
(github.com/hanzoai/livekit, which this fork now actually declares) and the
luxfi/metric repair in the parent commit that made this repo build at all.
2026-07-28 01:30:41 -07:00
..
2026-04-15 12:23:33 +05:30
2025-12-04 10:44:34 +05:30