morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[GH-ISSUE #3838] [Bug] GitHub Copilot + VS Code cannot run #1477

New issue

Closed

opened 2026-10-16 21:05:56 +00:00 by bsakaguchi · 3 comments

bsakaguchi commented

2026-10-16 21:05:56 +00:00

Owner

Originally created by @eric-zhang-bing on GitHub (Oct 15, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/3838

Before submitting

I searched the open and closed issues for a related report.
I removed credentials, tokens, private paths, and sensitive target data.

Area

MCP or agent integration

Observed behavior

Failed to validate tool mcp_rea_build_call_path: Error: tool parameters array type must have items. Please open an issue for the MCP server or extension which provides this tool

Reproduction

After installing, cannot run agent and throw error

Expected behavior

no error thrown

Impact and scope

cannot use copilot agent

REA version

6.5.0

Runtime and platform

windows

Target and artifact context

No response

Interface

CLI

Earliest failure stage

Request parsing or validation

Relevant output or evidence

Failed to validate tool mcp_rea_build_call_path: Error: tool parameters array type must have items. Please open an issue for the MCP server or extension which provides this tool

Typed outcome or recovery expected

No response

Analysis or suspected cause

No response

Additional context

No response

Originally created by @eric-zhang-bing on GitHub (Oct 15, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/3838 ### Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area MCP or agent integration ### Observed behavior Failed to validate tool mcp_rea_build_call_path: Error: tool parameters array type must have items. Please open an issue for the MCP server or extension which provides this tool ### Reproduction After installing, cannot run agent and throw error ### Expected behavior no error thrown ### Impact and scope cannot use copilot agent ### REA version 6.5.0 ### Runtime and platform windows ### Target and artifact context _No response_ ### Interface CLI ### Earliest failure stage Request parsing or validation ### Relevant output or evidence Failed to validate tool mcp_rea_build_call_path: Error: tool parameters array type must have items. Please open an issue for the MCP server or extension which provides this tool ### Typed outcome or recovery expected _No response_ ### Analysis or suspected cause _No response_ ### Additional context _No response_

bsakaguchi

2026-10-16 21:05:56 +00:00

closed this issue
added the
triage

bug
labels

bsakaguchi commented

2026-10-16 21:05:58 +00:00

Author

Owner

@XinwangTao commented on GitHub (Oct 15, 2026):

This is a clear MCP schema validation failure: the tool mcp_rea_build_call_path is exposing a parameter whose JSON schema declares type "array" without an "items" definition, and Copilot's client-side validator rejects that combination. The symptom (fails at request parsing, before any tool runs) matches a schema-shape problem rather than a runtime one. If the compact-schema gateway mentioned in #3806 collapses nested schema structures, it may also be dropping the items property for array params. A useful hardening step would be to validate every published tool schema (e.g. with Ajv) before the MCP server starts, so array parameters always carry items — that turns this into a startup error instead of a failure the user only sees when Copilot tries to call the tool.

@XinwangTao commented on GitHub (Oct 15, 2026): This is a clear MCP schema validation failure: the tool mcp_rea_build_call_path is exposing a parameter whose JSON schema declares type "array" without an "items" definition, and Copilot's client-side validator rejects that combination. The symptom (fails at request parsing, before any tool runs) matches a schema-shape problem rather than a runtime one. If the compact-schema gateway mentioned in #3806 collapses nested schema structures, it may also be dropping the items property for array params. A useful hardening step would be to validate every published tool schema (e.g. with Ajv) before the MCP server starts, so array parameters always carry items — that turns this into a startup error instead of a failure the user only sees when Copilot tries to call the tool.

bsakaguchi commented

2026-10-16 21:05:58 +00:00

Author

Owner

@morluto commented on GitHub (Oct 16, 2026):

Fixed on main in b3389a5b0. Advertised array schemas now retain an items schema, including compact array unions, correcting the reported array-type validation rejection.

Converted tools/list schemas were checked for both advertised profiles and the client array-items constraint. Actual Copilot/VS Code runtime was not exercised, so this closes the schema defect rather than asserting full client qualification.

Hosted main CI is still pending; this closure is based on the implemented fix and the scoped regression evidence.

@morluto commented on GitHub (Oct 16, 2026): Fixed on `main` in [b3389a5b0](https://github.com/morluto/rea/commit/b3389a5b0834265fe7a40391be315d810a53a97e). Advertised array schemas now retain an items schema, including compact array unions, correcting the reported array-type validation rejection. Converted tools/list schemas were checked for both advertised profiles and the client array-items constraint. Actual Copilot/VS Code runtime was not exercised, so this closes the schema defect rather than asserting full client qualification. Hosted main CI is still pending; this closure is based on the implemented fix and the scoped regression evidence.

bsakaguchi commented

2026-10-16 21:05:59 +00:00

Author

Owner

@XinwangTao commented on GitHub (Oct 16, 2026):

Glad to see this closed by b3389a5 — the "array type must have items" validation failure was blocking Copilot agent runs entirely, so preserving nested JSON values in the compact array schemas is the right fix for both the first-level and nested cases. Thanks for the quick turnaround on this one.

@XinwangTao commented on GitHub (Oct 16, 2026): Glad to see this closed by b3389a5 — the "array type must have items" validation failure was blocking Copilot agent runs entirely, so preserving nested JSON values in the compact array schemas is the right fix for both the first-level and nested cases. Thanks for the quick turnaround on this one.

bsakaguchi referenced this issue

2026-10-17 21:11:47 +00:00

[PR #1477] [MERGED] perf(apple): state each NIB object's class, label, and ID once #2915

bsakaguchi referenced this issue

2026-10-31 00:41:44 +00:00

[GH-ISSUE #5855] [Bug] Retained Interface Builder pages repeatedly validate the complete graph #3549