Fix standalone Valkey connection EOF

[chistopat]

Problem

rueidis tries CLUSTER topology discovery by default. Standalone Valkey (e.g. fsqr-valkey) returns error on CLUSTER command, causing EOF on connect.

Fix

Add ForceSingleClient: true to rueidis ClientOption — skips cluster discovery for standalone instances.

[github-actions]

Total coverage threshold (65%) satisfied: PASS
Total test coverage: 66.7% (1987/2980)

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ -0.05% (target: -1.00%)	✅ 0.00%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (48e3fd8)	6082	3045	50.07%
Head commit (32c1dd5)	6088 (+6)	3045 (+0)	50.02% (-0.05%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#18)	14	0	0.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[chistopat]

@greptile

[greptile-apps]

Greptile Summary

Fixed EOF error when connecting to standalone Valkey by adding ForceSingleClient: true to rueidis ClientOption. The fix adds a new WithStandalone() SDK option that skips cluster topology discovery, preventing the connection failure when standalone instances reject CLUSTER commands.

• Added Standalone bool field to internal/db/valkey/client.go:Config
• Wired it through pkg/sdk/options.go:clientConfig to SDK public API
• Passed to rueidis as ForceSingleClient option

The implementation is clean and follows existing patterns. Consider whether the Redis backend (internal/db/redis/client.go) needs the same fix, as standalone Redis instances also reject CLUSTER commands by default.

Confidence Score: 5/5

• Safe to merge — straightforward fix with clear intent
• Simple boolean flag addition following existing config patterns, no breaking changes, solves documented connection issue
• Consider applying same fix to internal/db/redis/client.go for standalone Redis instances

Important Files Changed

Filename	Overview
internal/db/valkey/client.go	Added Standalone field to Config and wired it to ForceSingleClient option to skip cluster discovery
pkg/sdk/client.go	Passed standalone config field through to Valkey store initialization
pkg/sdk/options.go	Added WithStandalone() option to disable cluster topology discovery

_{Last reviewed commit: 32c1dd5}