test(falkordb): skip when the port answers but is not FalkorDB

[guitelesc]

_connect() guards on ping(), which only proves something answers on 6379. A plain Redis — or an SSH tunnel forwarding one, which is what I hit — replies to PING but has no graph module, so the guard passes and both tests fail on unknown command 'GRAPH.QUERY' instead of skipping.

The module docstring says these are a no-op outside CI. That holds only because CI has nothing on 6379: the guard was validated against the empty case, never against a wrong occupant. A dev box with a Redis already on that port is exactly where it breaks.

The fix

Probe GRAPH.LIST after the ping, so the guard identifies the service rather than mere liveness. It is read-only, creates no keys, and anything that is not FalkorDB/RedisGraph rejects it as an unknown command:

probe	FalkorDB	plain Redis
PING	✅ True	✅ True — the bug
GRAPH.LIST	✅ []	❌ unknown command
MODULE LIST	✅ has graph	✅ [] — succeeds on both, needs content parsing

The two failure modes now skip with distinct messages (unreachable vs. wrong service).

Testing

Verified against all three environments, including the one that matters most — a guard that always skips would "fix" the failure while silently disabling the tests forever:

plain Redis on the port   -> 2 skipped  (was 2 failed)
falkordb/falkordb:latest  -> 2 passed   (guard does not over-skip)
nothing listening         -> 2 skipped

uv run pytest tests/ -q — 5086 passed, 11 skipped, 0 failed.

No automated regression test: reproducing this needs a wrong-service-on-the-port, i.e. the external service the default CI deliberately avoids. Happy to add one behind a marker if you'd prefer it.

🤖 Generated with Claude Code

[graphify-labs]

Graphify reviewed this change.

Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).

---

Graphify review — findings

Tightens the FalkorDB integration test's connection guard to skip—rather than fail—when a non-FalkorDB server answers on the port. _connect now follows its ping() liveness check with a read-only GRAPH.LIST probe, so a plain Redis (or an SSH tunnel forwarding one) that lacks the graph module is detected and skipped instead of erroring out on unknown command 'GRAPH.QUERY'.

No blocking issues surfaced.

Analysis details — impact, health, verification

Impact & health

Graphify review

Impact — 8 functions depend on the 8 functions this change touches.

Health — grade A; no new coupling hotspots.

Verification — 8 functions in the blast radius were not formally verified this run (proofs are advisory here).

Gate & verification

graphify gate

PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.

Advisory (not blocking):

• verification_scope: 8 function(s) in the blast radius were not formally verified this run

[safishamsi]

Shipped in v0.9.51 via authorship-preserving cherry-pick so you keep contributor-graph credit. Thanks @guitelesc! Release: https://github.com/Graphify-Labs/graphify/releases/tag/v0.9.51