Labels: bug, high-priority
Problem
src/redis.ts:29 creates new Redis(url) but never attaches an error event listener. The ioredis library emits an error event when the connection fails or drops — with no listener, Node.js treats it as an unhandled error and crashes the process.
This means any transient Redis outage (network blip, server restart, etc.) kills the entire test run.
Location
src/redis.ts:29
Suggested fix
Add an error event handler on the Redis client that logs the error and attempts reconnection:
client = new Redis(url);
client.on("error", (err) => {
logger.error({ err }, "Redis connection error");
});
Also consider adding a reconnect strategy so transient failures don't permanently disable caching mid-test.
Labels: bug, high-priority
Problem
src/redis.ts:29createsnew Redis(url)but never attaches anerrorevent listener. Theioredislibrary emits anerrorevent when the connection fails or drops — with no listener, Node.js treats it as an unhandled error and crashes the process.This means any transient Redis outage (network blip, server restart, etc.) kills the entire test run.
Location
src/redis.ts:29Suggested fix
Add an
errorevent handler on the Redis client that logs the error and attempts reconnection: