chore(mcp): fix mcp ready_pattern for hono runtime#60291
Merged
Conversation
Generated-By: PostHog Code Task-Id: bde5d4e1-5bf9-453f-b92f-a7d4561d68bd
Contributor
|
🎭 Playwright didn't run on this PR — your changes touch code that could affect E2E behavior, but Playwright is opt-in via label now to keep CI cost down. Add the Most PRs don't need this. Real regressions still get caught on master and fix-forward. |
Contributor
|
Reviews (1): Last reviewed commit: "chore(mcp): fix mcp ready_pattern for ho..." | Re-trigger Greptile |
Contributor
|
Size Change: 0 B Total Size: 80.2 MB ℹ️ View Unchanged
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
bin/mprocs.yamlready_pattern formcpwasReady on *— a leftover from the wrangler-era output. After the move to Hono, the server logs[MCP] Server started on 0.0.0.0:8787, so phrocs never marked the proc ready and kept it in starting/running limbo.Changes
ready_pattern: 'Ready on *'→'Server started on'tech: Python→Node(Hono runtime)How did you test this code?
Agent-authored. No automated tests added — config-only change.
Publish to changelog?
no
🤖 Agent context
PostHog Code agent. Located the mismatch by grepping the hono entrypoint for the actual ready log line and comparing to
bin/mprocs.yaml.Created with PostHog Code