Skip to content

fix: report npm bridge transport errors - #36

Merged
SanjithSambath merged 1 commit into
mainfrom
fix/npm-bridge-error-reporting
Jul 29, 2026
Merged

fix: report npm bridge transport errors#36
SanjithSambath merged 1 commit into
mainfrom
fix/npm-bridge-error-reporting

Conversation

@SanjithSambath

Copy link
Copy Markdown
Contributor

Summary

  • report hosted and stdio transport/protocol errors to stderr instead of dropping them
  • preserve stdout for JSON-RPC and leave shutdown, exit-code, timeout, and SDK retry behavior unchanged
  • bump the npm bridge to 1.0.2 so the merged fix is published by the release workflow

Why

The bridge did not install client.onerror or server.onerror handlers. Errors delivered through those SDK callbacks therefore had no diagnostic output, leaving operators without the underlying hosted or stdio failure.

This PR deliberately does not claim to fix silent process exit. The real Streamable HTTP transport does not emit onclose for network failures. A POST SSE response that ends cleanly without a JSON-RPC response can also remain pending until the SDK request timeout; that SDK-level behavior is outside this observability patch.

Testing

  • pnpm test
  • bridge regression test verifies hosted and stdio errors are written to stderr

@mcp-use

mcp-use Bot commented Jul 29, 2026

Copy link
Copy Markdown

Deployment #103 deployed successfully

StatusLogsURLUpdated
ReadyBuild Logs | Runtime Logs🔗 MCP URLJul 29 2026 12:22 am

View deployment details


Deployed on Manufact.com

@SanjithSambath
SanjithSambath merged commit fc2181f into main Jul 29, 2026
5 checks passed
@SanjithSambath
SanjithSambath deleted the fix/npm-bridge-error-reporting branch July 29, 2026 00:30
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