[GH-ISSUE #8658] Windows: JavaScript analysis fails during parent source-transfer with EPERM #7502

New issue

Open

opened 2026-11-03 00:30:18 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-03 00:30:18 +00:00

Owner

Originally created by @lovemiir1019 on GitHub (Nov 2, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/8658

REA 6.7.0 on Windows x64, using Node.js 24.11.1, failed during analyze-javascript-application.

The saved result reports:

Exit code: 1
Error: execution_failure
Provider: javascript-static-analysis
Phase: source-transfer
Retryable: false
Underlying error: EPERM while opening the temporary .source file

Static inspection places this operation in the parent-side JavaScriptAnalysisWorker: after the worker startup handshake, the parent calls fs/promises.writeFile with exclusive creation (wx), mode 0600, and the deadline signal. The request frame is sent only after that write completes. The corresponding pathname write remains in the 6.8.0 release source. Version 6.8.0 was source-inspected, not executed for this report.

The failing REA process’s AppContainer state and actual runtime DACL were not measured. The underlying Win32 API and status are also unconfirmed. This report therefore does not establish an AppContainer-specific root cause or a particular ACL defect.

Could you clarify:

Is this JavaScript parent/child file-transfer path supported for restricted or AppContainer callers?
Is there an official fix or supported configuration that preserves the private-runtime protections?
What bounded diagnostic should be collected to identify the failing operation? Ideally, it would correlate the failing parent process’s Node error fields, TokenIsAppContainer boolean, and verified native operation/status without exposing source contents, personal paths, SIDs, or credentials.

Related context: #5225 concerns Ghidra snapshot admission under AppContainer. It is a different operation and is not evidence that this JavaScript failure has the same cause.

Relevant release sources:

Originally created by @lovemiir1019 on GitHub (Nov 2, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/8658 REA 6.7.0 on Windows x64, using Node.js 24.11.1, failed during `analyze-javascript-application`. The saved result reports: - Exit code: `1` - Error: `execution_failure` - Provider: `javascript-static-analysis` - Phase: `source-transfer` - Retryable: `false` - Underlying error: `EPERM` while opening the temporary `.source` file Static inspection places this operation in the parent-side `JavaScriptAnalysisWorker`: after the worker startup handshake, the parent calls `fs/promises.writeFile` with exclusive creation (`wx`), mode `0600`, and the deadline signal. The request frame is sent only after that write completes. The corresponding pathname write remains in the 6.8.0 release source. Version 6.8.0 was source-inspected, not executed for this report. The failing REA process’s AppContainer state and actual runtime DACL were not measured. The underlying Win32 API and status are also unconfirmed. This report therefore does **not** establish an AppContainer-specific root cause or a particular ACL defect. Could you clarify: 1. Is this JavaScript parent/child file-transfer path supported for restricted or AppContainer callers? 2. Is there an official fix or supported configuration that preserves the private-runtime protections? 3. What bounded diagnostic should be collected to identify the failing operation? Ideally, it would correlate the failing parent process’s Node error fields, `TokenIsAppContainer` boolean, and verified native operation/status without exposing source contents, personal paths, SIDs, or credentials. Related context: #5225 concerns Ghidra snapshot admission under AppContainer. It is a different operation and is not evidence that this JavaScript failure has the same cause. Relevant release sources: - [6.7.0 parent source-transfer](https://github.com/morluto/rea/blob/rea-agents-6.7.0/src/javascript/analysis/JavaScriptAnalysisWorker.ts#L181-L197) - [6.8.0 parent source-transfer](https://github.com/morluto/rea/blob/rea-agents-6.8.0/src/javascript/analysis/JavaScriptAnalysisWorker.ts#L293-L298)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#7502

No description provided.

Rows
Columns