Skip to content

fix(ci): start Redis before the MCP server; fail fast when MCP never comes up - #3056

Open
gewenyu99 wants to merge 1 commit into
mainfrom
posthog-code/ci-redis-and-fatal-mcp-gate
Open

fix(ci): start Redis before the MCP server; fail fast when MCP never comes up#3056
gewenyu99 wants to merge 1 commit into
mainfrom
posthog-code/ci-redis-and-fatal-mcp-gate

Conversation

@gewenyu99

Copy link
Copy Markdown
Contributor

Every wizard-ci cell has been failing since posthog master's MCP hono server began hard-exiting without Redis ([MCP] Failed to connect to Redis … process.exit(1) at services/mcp/src/hono/index.ts). The workflow never started one, the readiness loop only warned, and each matrix cell then ran a full agent that failed at the dashboard task — ~40 wasted LLM runs per trigger reporting an infra outage as wizard failures.

Two changes in the Run Wizard CI step: start Redis before the MCP server (docker on ubuntu, brew fallback on the macos/swift runner, apt as last resort), and make the 2-minute MCP readiness timeout a hard ::error + exit 1.


Created with PostHog Code

…comes up

posthog services/mcp (hono) hard-exits without Redis at localhost:6379,
so every wizard-ci cell lost its MCP and reported an agent failure per
app. Start Redis first (docker/brew/apt per runner OS) and turn the
2-minute MCP readiness warning into a hard error so infra outages fail
one step early instead of burning a full agent run per matrix cell.

Generated-By: PostHog Code
Task-Id: 2d43c175-646e-4d73-a974-760280c8c95b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant