:bug: github issue agent fails due to incompatibility with openai
维护者通常 8 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with a reproduction of the git-issue-agent failure using OpenAI, then inspect a2a/git_issue_agent/pyproject.toml and pkg/github/issues.go:543-551. Capture the tool schema on the wire and compare it with the resolved crewai-tools and OpenAI versions. Done means the cause is confirmed and the agent can run without the invalid null parameters error.
由索引模型根据 Issue 内容生成。
描述
Describe the bug
The problem: the git-issue-agent fails before any tool runs:
400 Invalid schema for function 'list_issue_types':
None is not of type 'object', 'boolean'
Steps To Reproduce
Use the agent with open ai
I only verified it with Token Broker - I need to verify it with token exchange or understand why (in case it only happened with token-broker)
Expected Behavior
Cause: crewai-tools converts MCP tool schemas into OpenAI function definitions and emits parameters: null for that tool. OpenAI 2.45.0 rejects null. The MCP server's own schema is valid — I read it at pkg/github/issues.go:543-551, a proper {type: "object", properties: {owner}, required: ["owner"]}.
Why now: a2a/git_issue_agent/pyproject.toml uses floors, not pins — crewai-tools[mcp]>=1.15.2, openai unpinned. Rebuilding resolved openai 2.45.0. Tellingly, that file's own comments discuss pinning around openai 2.24.0/2.30.0, so the resolved set has drifted well past what the code was written against.
Caveat: this is inferred from the error plus the version drift. I never captured the actual schema on the wire — my attempt to enable MCP command logging wrote to a file rather than stdout, and I reverted it. So "crewai-tools mangles it" is the strong hypothesis, not a proven fact. Worth confirming before pinning blindly.
Rossoctl Version
No response
Additional Context
No response
- 主要语言
- Python
- 星标
- 11
- 派生
- 42
- 平均合并
- 4 天 4 小时
- 30 天内合并 PR
- 39
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
rossoctl/examples 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 8 天内回复
-
难度 1/5 1 小时以内 新手友好度 25/100
rossoctl/examples#986 · 2 条评论 ·
维护者通常 8 天内回复
-
难度 2/5 1-3 小时 新手友好度 25/100
rossoctl/examples#985 · 2 条评论 ·
维护者通常 8 天内回复
-
难度 1/5 1 小时以内 新手友好度 30/100
rossoctl/examples#984 · 2 条评论 ·
维护者通常 8 天内回复
-
难度 1/5 1 小时以内 新手友好度 35/100
rossoctl/examples#983 · 2 条评论 ·
维护者通常 8 天内回复
查看 rossoctl/examples 的全部 Issue
相似的 Issue
-
Python Volcengine provider returns failures instead of raising them可能已有人在做 @Ricardo-M-L 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 79/100
agent-infra/sandbox#248 ·
-
Textractor leaves empty temporary files when remote retrieval fails可能已有人在做 @HuaTNA 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
test(bm_generation): pin the learning parameters and CPU sync shortcut可能已有人在做 @iloveeyjafjalla 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
qboson/kaiwu-pytorch-plugin#1341 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
elder-plinius/V3R1T4S#625 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复