[GH-ISSUE #7303] [Bug] compare_wasm_interfaces does not say which Evidence argument it rejected #4339

New issue

Closed

opened 2026-10-31 00:49:02 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:49:02 +00:00

Owner

Originally created by @Adolanium on GitHub (Oct 26, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/7303

Before submitting

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

Area

Evidence, artifacts, or reconstruction

Observed behavior

When compare_wasm_interfaces rejects the inspect_wasm_artifact Evidence supplied as left or right (for example a tampered result or a rebound subject), the AnalysisInputError issue has path: []. It does not say which argument was rejected.

Reproduction

Ran on Linux (WSL Ubuntu, Node 24.22.1) at upstream/main e1ec737d9, calling compareWasmInterfaces with valid left Evidence and right Evidence whose interface entry name was edited after creation: the error issue path is [].

Expected behavior

The issue path names the rejected argument, ["left"] or ["right"].

Impact and scope

A caller or agent correcting the request cannot tell which of the two Evidence inputs to replace.

REA version

revision e1ec737d9

Runtime and platform

Linux (WSL Ubuntu), Node 24.22.1

Target and artifact context

Fixture Wasm inspection Evidence.

Interface

MCP

Earliest failure stage

Request parsing or validation

Relevant output or evidence

Root cause and fix are in #7302, with the regression test.

Typed outcome or recovery expected

AnalysisInputError with an issue at ["left"] or ["right"].

Analysis or suspected cause

Root cause and fix are in #7302.

Additional context

Fixed by #7302.

Originally created by @Adolanium on GitHub (Oct 26, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7303 ### 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 Evidence, artifacts, or reconstruction ### Observed behavior When `compare_wasm_interfaces` rejects the `inspect_wasm_artifact` Evidence supplied as `left` or `right` (for example a tampered result or a rebound subject), the `AnalysisInputError` issue has `path: []`. It does not say which argument was rejected. ### Reproduction Ran on Linux (WSL Ubuntu, Node 24.22.1) at upstream/main e1ec737d9, calling `compareWasmInterfaces` with valid `left` Evidence and `right` Evidence whose interface entry name was edited after creation: the error issue path is `[]`. ### Expected behavior The issue path names the rejected argument, `["left"]` or `["right"]`. ### Impact and scope A caller or agent correcting the request cannot tell which of the two Evidence inputs to replace. ### REA version revision `e1ec737d9` ### Runtime and platform Linux (WSL Ubuntu), Node 24.22.1 ### Target and artifact context Fixture Wasm inspection Evidence. ### Interface MCP ### Earliest failure stage Request parsing or validation ### Relevant output or evidence Root cause and fix are in #7302, with the regression test. ### Typed outcome or recovery expected `AnalysisInputError` with an issue at `["left"]` or `["right"]`. ### Analysis or suspected cause Root cause and fix are in #7302. ### Additional context Fixed by #7302.

bsakaguchi referenced this issue

2026-10-31 01:12:30 +00:00

[PR #4339] docs: add CLAUDE.md orientation for Claude Code #6184

bsakaguchi referenced this issue

2026-11-01 21:10:54 +00:00

[GH-ISSUE #3795] [Tracker] Open documentation issues and pull requests (October 2026) #1468

bsakaguchi closed this issue

2026-11-04 12:09:22 +00:00