[GH-ISSUE #2121] [Bug] inspect-managed-members --type with a repeated or empty name reports execution_failure and recommends rea doctor #691

New issue

Closed

opened 2026-10-15 18:27:27 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:27:27 +00:00

Owner

Originally created by @kaoru0822-kitauji on GitHub (Oct 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/2121

Observed behavior

rea inspect-managed-members --type accepts a repeated or empty type name, then fails with a generic execution error that sends the caller to rea doctor:

$ rea inspect-managed-members /path/Microsoft.PowerShell.Pager.dll --type Microsoft.PowerShell.Pager --type Microsoft.PowerShell.Pager --format json
{"code":"execution_failure", "message":"Analysis could not complete. Run `rea doctor` and review the reported details; repeating the unchanged request is not expected to succeed.", "details":{"provider_id":"rea-dotnet-static","operation":"inspect_managed_members"}}

$ rea inspect-managed-members /path/Microsoft.PowerShell.Pager.dll --type "" --format json
(same execution_failure)

Nothing is wrong with the environment or the assembly; the request repeats a name / passes an empty name. The MCP tool rejects the same input at its boundary as invalid (type_names is min(1) strings, at least one item, type_names must not repeat a name).

Reproduction

Any managed assembly works, e.g. the PSReadLine Microsoft.PowerShell.Pager.dll shipped inside VS Code (Contents/Resources/app/out/vs/workbench/contrib/terminal/common/scripts/psreadline/). Current main c22111eca.

Expected behavior

A validation error that names --type and the problem (repeated / empty name), as other CLI options with contract constraints do.

Cause

src/cli/managedCommands.ts declares --type as z.array(z.string()) instead of reusing managedMembersInputSchema.shape.type_names. The looser input reaches ManagedStaticProvider, whose managedMembersInputSchema.parse(...) throws a ZodError that is projected as execution_failure.

Originally created by @kaoru0822-kitauji on GitHub (Oct 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/2121 ### Observed behavior `rea inspect-managed-members --type` accepts a repeated or empty type name, then fails with a generic execution error that sends the caller to `rea doctor`: ```text $ rea inspect-managed-members /path/Microsoft.PowerShell.Pager.dll --type Microsoft.PowerShell.Pager --type Microsoft.PowerShell.Pager --format json {"code":"execution_failure", "message":"Analysis could not complete. Run `rea doctor` and review the reported details; repeating the unchanged request is not expected to succeed.", "details":{"provider_id":"rea-dotnet-static","operation":"inspect_managed_members"}} $ rea inspect-managed-members /path/Microsoft.PowerShell.Pager.dll --type "" --format json (same execution_failure) ``` Nothing is wrong with the environment or the assembly; the request repeats a name / passes an empty name. The MCP tool rejects the same input at its boundary as invalid (`type_names` is `min(1)` strings, at least one item, `type_names must not repeat a name`). ### Reproduction Any managed assembly works, e.g. the PSReadLine `Microsoft.PowerShell.Pager.dll` shipped inside VS Code (`Contents/Resources/app/out/vs/workbench/contrib/terminal/common/scripts/psreadline/`). Current main c22111eca. ### Expected behavior A validation error that names `--type` and the problem (repeated / empty name), as other CLI options with contract constraints do. ### Cause `src/cli/managedCommands.ts` declares `--type` as `z.array(z.string())` instead of reusing `managedMembersInputSchema.shape.type_names`. The looser input reaches `ManagedStaticProvider`, whose `managedMembersInputSchema.parse(...)` throws a ZodError that is projected as `execution_failure`.

bsakaguchi

2026-10-15 18:27:27 +00:00