Werkdock's quirk table listed redis as moving its port through
REDIS_PORT. Redis does not read it, so up to werkdock 0.7.0 the port
Testcontainers was given had nothing listening on it — and no test here
would have noticed, because every test was a PostgreSQL one.
This is the cheapest possible guard against that class of mistake: a
GenericContainer, no client library, PING and PONG over a plain socket.
It asks the only question that matters — is a server really answering
where werkdock said it would — and it asks it about an image that is not
a database, which is where the table was wrong.
Needs werkdock 0.8.0 and redis:7-alpine in the store.
Werkdock's quirk table listed redis as moving its port through
REDIS_PORT. Redis does not read it, so up to werkdock 0.7.0 the port
Testcontainers was given had nothing listening on it — and no test here
would have noticed, because every test was a PostgreSQL one.
This is the cheapest possible guard against that class of mistake: a
GenericContainer, no client library, PING and PONG over a plain socket.
It asks the only question that matters — is a server really answering
where werkdock said it would — and it asks it about an image that is not
a database, which is where the table was wrong.
Needs werkdock 0.8.0 and redis:7-alpine in the store.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Werkdock's quirk table listed redis as moving its port through
REDIS_PORT. Redis does not read it, so up to werkdock 0.7.0 the port
Testcontainers was given had nothing listening on it — and no test here
would have noticed, because every test was a PostgreSQL one.
This is the cheapest possible guard against that class of mistake: a
GenericContainer, no client library, PING and PONG over a plain socket.
It asks the only question that matters — is a server really answering
where werkdock said it would — and it asks it about an image that is not
a database, which is where the table was wrong.
Needs werkdock 0.8.0 and redis:7-alpine in the store.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Werkdock's quirk table listed redis as moving its port through
REDIS_PORT. Redis does not read it, so up to werkdock 0.7.0 the port
Testcontainers was given had nothing listening on it — and no test here
would have noticed, because every test was a PostgreSQL one.
This is the cheapest possible guard against that class of mistake: a
GenericContainer, no client library, PING and PONG over a plain socket.
It asks the only question that matters — is a server really answering
where werkdock said it would — and it asks it about an image that is not
a database, which is where the table was wrong.
Needs werkdock 0.8.0 and redis:7-alpine in the store.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com