Remove context7 from scout workflow to fix gateway timeout #11817
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.
Scout workflow failing due to MCP Gateway hanging indefinitely during
context7server initialization. Gateway successfully launchesarxivbut blocks waiting forcontext7response, never starts HTTP server, health check times out after 120s.Changes
Technical Details
Gateway logs show successful initialization of other servers but hang at:
No timeout exists for individual MCP server launches. The
context7container starts but never completes MCP protocol handshake, blocking all subsequent initialization.Follow-up
mcp-inspectorworkflow also imports context7 and has similar failuresOriginal prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.