Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Execution failed: Failed to refresh MCP tools for server github-mcp-server; the last catalog is stale

未关闭
#4,077 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
github

调研方向

Start in the GitHub Copilot app at /chat on Windows 10.0.26200 with app version 1.1.22, invoking github-mcp-server-web_search repeatedly and comparing the behavior with the Copilot CLI. Done means the MCP tool invokes reliably without the stale-catalog or GitHub credential-registration error.

由索引模型根据 Issue 内容生成。

描述

Using the GitHub copilot app in the past week, most of the time when a session tries to use the "github-mcp-server-web_search" tool, it fails, and the tool gives the following error response:

"MCP tool catalog changed before tool "github-mcp-server-web_search" could be invoked: Failed to verify cached MCP tools: MCP request failed: Transport send error: Transport [mcp::client::ToolListRevisionTransport<rmcp::transport::worker::WorkerTransport<rmcp::transport::streamable_http_client::StreamableHttpClientWorker<mcp::client::DiscoverFallbackHttpClient<mcp::dynamic_headers::HeaderRefreshHttpClientmcp::client::RawCapturingReqwestClient>>>>] error: unexpected server response: dynamic header provider failed: GitHub credential registration is no longer available for this session"

Then, the agent will give the following message:

Execution failed: Failed to refresh MCP tools for server github-mcp-server; the last catalog is stale.

This does not happen EVERY time... just most of the time. This just started happening about a week ago. The copilot CLI never has this problem. It works every time.

I have tried refreshing my GitHub auth, restarting the app, reinstalling the app. Nothing works.

Has anyone else experienced this?


Field Value
App version 1.1.22
OS Windows 10.0.26200
Theme GitHub
Path /chat
Tenure Week 16
主要语言
没有语言数据
星标
2.1k
派生
157
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

github/app 的其他 Issue

查看 github/app 的全部 Issue

相似的 Issue

更多 Security Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。