[GH-ISSUE #7954] [Bug] Investigate Hopper bootstrap Python script execution failure #4653

New issue

Open

opened 2026-10-31 00:51:57 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-31 00:51:57 +00:00

Owner

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

Before submitting

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

Area

Native analysis or decompilation

Observed behavior

A user reported that Hopper completed background analysis of an AArch64 Mach-O, then displayed Cannot execute Python script for REA's temporary bootstrap.py. The REA command or MCP request and the client-side outcome are unknown.

Reproduction

NOT_ENOUGH_INFO: The original command, target, client, and exact steps are unavailable. This was reported once; no independent reproduction has been performed.

Expected behavior

REA's Hopper bridge should start when Hopper runs its bootstrap. If it cannot, the caller should receive an actionable failure and truthful cleanup state. The log alone does not establish whether the bridge started before subsequently ending.

Impact and scope

A script failure was visible in Hopper. Whether the requested REA analysis completed, whether evidence was retained, and whether cleanup or retry was affected are unknown. Frequency and other platforms are untested.

REA version

NOT_ENOUGH_INFO: The full REA runtime version and revision are unknown. The bootstrap referenced a bridge source in a checkout at 5082b50f074e2f3e1ba5534d119ae16566673a36; this does not establish the runtime version.

Runtime and platform

macOS 26.3, arm64. A running Hopper process was observed locally; the installed app identifies as 6.6.0-demo. Its mapped libraries included Python 3.12. The Node.js version and whether that process was the one that produced the reported log are unknown.

Target and artifact context

AArch64 Mach-O, as reported by Hopper. Target identity and provenance are unknown.

Interface

Unknown (CLI or MCP client not identified).

Earliest failure stage

Unknown; the first observed symptom is Hopper's script-execution message.

Relevant output or evidence

User-provided Hopper output (temporary session path redacted):

Last pass done
Background analysis ended in 0ms
Executing Python script "/private/tmp/<session>/bootstrap.py"
Cannot execute Python script "/private/tmp/<session>/bootstrap.py"

Read-only follow-up: the bootstrap and its referenced bridge source existed; the bridge parsed with Python 3.12. A subsequent local inspection found no bridge socket and no Python traceback in the sampled Hopper system log. The inspected Hopper process and REA connection could not be tied conclusively to the original client. No credentials or bootstrap contents are included.

Analysis or suspected cause

NOT_ENOUGH_INFO: The log does not show a Python exception. Check whether Hopper failed to execute the bootstrap, the bridge raised during startup, or an already-started bridge ended after client disconnect. Capture the caller's structured REA result and cleanup state, and reproduce with a disposable target before drawing a conclusion.

Additional context

Related: #2975 covers a separate observed recovery failure after Hopper exits, including demo expiry. No expiry dialog was reported here; this report does not establish that the 30-minute demo limit caused the script message.

Originally created by @morluto on GitHub (Oct 29, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7954 ### 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 Native analysis or decompilation ### Observed behavior A user reported that Hopper completed background analysis of an AArch64 Mach-O, then displayed `Cannot execute Python script` for REA's temporary `bootstrap.py`. The REA command or MCP request and the client-side outcome are unknown. ### Reproduction NOT_ENOUGH_INFO: The original command, target, client, and exact steps are unavailable. This was reported once; no independent reproduction has been performed. ### Expected behavior REA's Hopper bridge should start when Hopper runs its bootstrap. If it cannot, the caller should receive an actionable failure and truthful cleanup state. The log alone does not establish whether the bridge started before subsequently ending. ### Impact and scope A script failure was visible in Hopper. Whether the requested REA analysis completed, whether evidence was retained, and whether cleanup or retry was affected are unknown. Frequency and other platforms are untested. ### REA version NOT_ENOUGH_INFO: The full REA runtime version and revision are unknown. The bootstrap referenced a bridge source in a checkout at `5082b50f074e2f3e1ba5534d119ae16566673a36`; this does not establish the runtime version. ### Runtime and platform macOS 26.3, arm64. A running Hopper process was observed locally; the installed app identifies as 6.6.0-demo. Its mapped libraries included Python 3.12. The Node.js version and whether that process was the one that produced the reported log are unknown. ### Target and artifact context AArch64 Mach-O, as reported by Hopper. Target identity and provenance are unknown. ### Interface Unknown (CLI or MCP client not identified). ### Earliest failure stage Unknown; the first observed symptom is Hopper's script-execution message. ### Relevant output or evidence User-provided Hopper output (temporary session path redacted): ```text Last pass done Background analysis ended in 0ms Executing Python script "/private/tmp/<session>/bootstrap.py" Cannot execute Python script "/private/tmp/<session>/bootstrap.py" ``` Read-only follow-up: the bootstrap and its referenced bridge source existed; the bridge parsed with Python 3.12. A subsequent local inspection found no bridge socket and no Python traceback in the sampled Hopper system log. The inspected Hopper process and REA connection could not be tied conclusively to the original client. No credentials or bootstrap contents are included. ### Analysis or suspected cause NOT_ENOUGH_INFO: The log does not show a Python exception. Check whether Hopper failed to execute the bootstrap, the bridge raised during startup, or an already-started bridge ended after client disconnect. Capture the caller's structured REA result and cleanup state, and reproduce with a disposable target before drawing a conclusion. ### Additional context Related: #2975 covers a separate observed recovery failure after Hopper exits, including demo expiry. No expiry dialog was reported here; this report does not establish that the 30-minute demo limit caused the script message.

bsakaguchi added the

bug

triage

labels

2026-10-31 00:51:57 +00:00

bsakaguchi commented

2026-10-31 00:51:59 +00:00

Author

Owner

@aakash-env commented on GitHub (Oct 30, 2026):

@morluto @baron @monomyth kindly assign this issue to me

@aakash-env commented on GitHub (Oct 30, 2026): @morluto @baron @monomyth kindly assign this issue to me