morluto/rea

Fork 0

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

macOS 环境。 #454

New issue

Closed

opened 2026-10-15 18:25:12 +00:00 by bsakaguchi · 3 comments

bsakaguchi commented

2026-10-15 18:25:12 +00:00

Owner

Originally created by @bool2002 on GitHub (Oct 9, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/1262

Before submitting

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

Area

Process capture or runtime observation

Current limitation

REA 的 Android/JADX 流程在当前 Windows 宿主上不可用，需要受支持的 Linux/macOS 环境。
能否支持在windows 使用

Use cases

在初始化项目的时候，codex 提示部分功能只能在ios上使用

Desired outcome and success criteria

在我们初始化的时候都会出现

Authority boundaries and non-goals

No response

Alternatives considered

No response

Possible direction

No response

References

No response

Originally created by @bool2002 on GitHub (Oct 9, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/1262 ### Before submitting - [x] I searched the open and closed issues and pull requests for a related proposal. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area Process capture or runtime observation ### Current limitation REA 的 Android/JADX 流程在当前 Windows 宿主上不可用，需要受支持的 Linux/macOS 环境。能否支持在windows 使用 ### Use cases 在初始化项目的时候，codex 提示部分功能只能在ios上使用 ### Desired outcome and success criteria 在我们初始化的时候都会出现 ### Authority boundaries and non-goals _No response_ ### Alternatives considered _No response_ ### Possible direction _No response_ ### References _No response_

bsakaguchi

2026-10-15 18:25:12 +00:00

closed this issue
added the
area: build

area: cli

area: mcp

enhancement

P2: medium

area: tests
labels

bsakaguchi commented

2026-10-15 18:25:13 +00:00

Author

Owner

@rahul9142356693-ui commented on GitHub (Oct 9, 2026):

@rahul9142356693-ui commented on GitHub (Oct 9, 2026): Hi

bsakaguchi commented

2026-10-15 18:25:13 +00:00

Author

Owner

@N0zoM1z0 commented on GitHub (Oct 9, 2026):

Confirmed on current source: this is an explicit Windows host rejection in the Android provider, rather than a JADX instruction-set limitation. The existing Windows Job Object launcher supports owned stdout/stderr and cleanup but rejects writable protocol stdin; JADX requires bidirectional stdio.

The requested fix must add that stream within the existing atomic Job Object authority, then exercise Windows CLI/MCP analysis, cancellation, abnormal exits and descendant cleanup with real Java/JADX. Removing only the platform check would leave the underlying launch failure. A native Windows x64 host is available for this verification; no provider installation or device/emulator access is implied.

Implementation and real verification are being tracked with the current maintenance batch. Existing Linux/macOS behavior and caller-supplied JDK/JAR requirements remain part of the boundary.

@N0zoM1z0 commented on GitHub (Oct 9, 2026): Confirmed on current source: this is an explicit Windows host rejection in the Android provider, rather than a JADX instruction-set limitation. The existing Windows Job Object launcher supports owned stdout/stderr and cleanup but rejects writable protocol stdin; JADX requires bidirectional stdio. The requested fix must add that stream within the existing atomic Job Object authority, then exercise Windows CLI/MCP analysis, cancellation, abnormal exits and descendant cleanup with real Java/JADX. Removing only the platform check would leave the underlying launch failure. A native Windows x64 host is available for this verification; no provider installation or device/emulator access is implied. Implementation and real verification are being tracked with the current maintenance batch. Existing Linux/macOS behavior and caller-supplied JDK/JAR requirements remain part of the boundary.

bsakaguchi commented

2026-10-15 18:25:13 +00:00

Author

Owner

@N0zoM1z0 commented on GitHub (Oct 9, 2026):

Fixed and merged in #1276. After integrating current main, the matching rebuilt Windows native component passed the full native control verifier, including protocol-input backpressure, copied-buffer integrity, EOF, pending-write cancellation, owned-child settlement and unrelated-process preservation.

The real Windows Android workflow also passed again: all five MCP operations, CLI package-information parity, Chinese/space input paths, unchanged APK digest, SDK output validation and session cleanup. Both final guarded runs observed no remaining owned processes. Earlier lifecycle verification covered cancellation, disconnect/reuse and forced CLI-owner exit; forced exit kills the owned Java process but can leave temporary workspace files, which remain an explicit limitation. These were source-built checks with existing JDK/JADX prerequisites, not a newly published npm release.

@N0zoM1z0 commented on GitHub (Oct 9, 2026): Fixed and merged in #1276. After integrating current main, the matching rebuilt Windows native component passed the full native control verifier, including protocol-input backpressure, copied-buffer integrity, EOF, pending-write cancellation, owned-child settlement and unrelated-process preservation. The real Windows Android workflow also passed again: all five MCP operations, CLI package-information parity, Chinese/space input paths, unchanged APK digest, SDK output validation and session cleanup. Both final guarded runs observed no remaining owned processes. Earlier lifecycle verification covered cancellation, disconnect/reuse and forced CLI-owner exit; forced exit kills the owned Java process but can leave temporary workspace files, which remain an explicit limitation. These were source-built checks with existing JDK/JADX prerequisites, not a newly published npm release.

bsakaguchi referenced this issue

2026-10-16 21:13:14 +00:00

[PR #454] [MERGED] fix(mcp): clarify target routing and caller diagnostics #2001

bsakaguchi added

enhancement

and removed

enhancement

labels

2026-10-31 00:29:10 +00:00