Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Ping on 2026-07-28 sessions sends a removed method and surfaces confusing errors - propose failing fast

Cerrado
  • ¿Algo no está bien?
#1,377 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
go
Área
api

Línea de trabajo

Read ClientSession.Ping in mcp/client.go and inspect the protocol version negotiated by the session. The issue describes a guard and a test that verifies no ping request is sent on a simulated 2026-07-28 session; it also mentions a cmd_test readiness check. Done means Ping returns a descriptive local error for that version and the tests cover the behavior. The author says a patch is ready and plans to send a PR after maintainer feedback.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Follow-up to #1249 / #1174 / #1130, which closed the missing-_meta reports as by design because ping is removed from the 2026-07-28 protocol schema. This issue is about the client-side consequence of that ruling.

What did you do? Connected to a discovery-native 2026-07-28 server (e.g. https://mcp.svelte.dev/mcp) and called ClientSession.Ping.

What did you see? The client sends the removed ping method anyway and surfaces the server's rejection: MCP error -32020: Header mismatch: MCP-Protocol-Version does not match the request protocol version on transports that validate header/meta consistency, or MethodNotFound at dispatch — neither of which tells the caller that the method no longer exists in the negotiated protocol.

What did you expect to see? A clear local error before any round trip, pointing at a liveness check that still works on 2026-07-28 sessions.

SDK version: v1.8.0 (behavior identical on current main: Ping in mcp/client.go sends unconditionally).

Go version: go1.27.1.

Proposal: on sessions negotiated at 2026-07-28, Ping returns a descriptive local error without a round trip — mcp: ping is not supported on 2026-07-28 sessions (the method was removed); verify liveness with tools/list, resources/list, or prompts/list — instead of sending a method the spec removed. No working behavior is lost: every such ping fails today. If this counts as an exported-API behavior change under the proposal process, happy to treat this issue as the proposal seed.

I have a patch ready (guard + a test asserting no ping request is sent on a simulated 2026-07-28 session, plus a cmd_test readiness check that no longer relies on ping) and will send the PR once there's a maintainer read on the direction.

Lenguaje dominante
Go
Estrellas
5.2k
Forks
583
Merge medio
1 d 13 h
PR fusionados (30 d)
53

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de modelcontextprotocol/go-sdk

Todos los issues de modelcontextprotocol/go-sdk

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.