Skip to content

Multi-Server MCPConfigTransport fails entire session if any server is unreachable #792

Multi-Server MCPConfigTransport fails entire session if any server is unreachable

Multi-Server MCPConfigTransport fails entire session if any server is unreachable #792

Triggered via issue March 26, 2026 14:02
Status Success
Total duration 1m 58s
Artifacts
marvin-dedupe-issues
1m 54s
marvin-dedupe-issues
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
marvin-dedupe-issues
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oven-sh/setup-bun@3d267786b128fe76c2f16a390aa2448b815359f3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
marvin-dedupe-issues
⚠️ SECURITY WARNING: Bypassing write permission check for rishid due to allowed_non_write_users='*'. This should only be used for workflows with very limited permissions.