morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 07:47:29 +00:00

[GH-ISSUE #8595] [Bug] Frida verifier cleanup fixture copies its dependency to the wrong path #6664

New issue

Closed

opened 2026-11-01 21:13:03 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-01 21:13:03 +00:00

Owner

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

Before submitting

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

Area

Other

Observed behavior

CI's providerVerifierCleanup.test.ts fails four Frida cases before exercising cleanup. The copied verify-frida.mjs imports dist/domain/fridaRemoteAddress.js, but the fixture creates a stub at dist/contracts/fridaRemoteAddress.js; Node reports ERR_MODULE_NOT_FOUND.

Reproduction

On exact main base d3ab0faf52a02ff5a618f3ed7beb608b78752abd, run npm run test:focused -- tests/boundary/process/providerVerifierCleanup.test.ts. On macOS arm64 with Node 24.22.1, four Frida cases failed with that missing module; four JEB cases passed. The same failure appeared in Linux CI test shard 4 and portable tests on #8591.

Expected behavior

The fixture should resolve the verifier's real built address-validation dependency so the controlled provider and cleanup outcomes reach the assertions. Keep this as an orchestration test; it does not prove real Frida behavior.

Impact and scope

The failure blocks the affected CI runs and prevents these four tests from exercising their intended cleanup paths. This does not establish a production verifier or real Frida bug.

REA version

Base commit d3ab0faf52a02ff5a618f3ed7beb608b78752abd.

Runtime and platform

Node 24.22.1; macOS arm64 local reproduction and Linux CI.

Target and artifact context

Synthetic engine-facing fixture, no real provider target.

Interface

Test/CI.

Earliest failure stage

Fixture module loading before verification or cleanup.

Relevant output or evidence

ERR_MODULE_NOT_FOUND: .../dist/domain/fridaRemoteAddress.js imported from the fixture's scripts/verify-frida.mjs. See #8591 CI.

Typed outcome or recovery expected

Resolve actual verifier dependencies, retain primary and cleanup errors, and preserve JEB controls. Do not infer real-provider behavior from this fixture.

Analysis or suspected cause

The verifier imports the domain path while the test still writes an unused contracts-path stub.

Additional context

cc @gensokyo-dev @kaoru0822-kitauji @N0zoM1z0

Originally created by @morluto on GitHub (Nov 1, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/8595 ### Before submitting - [x] I searched open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area Other ### Observed behavior CI's `providerVerifierCleanup.test.ts` fails four Frida cases before exercising cleanup. The copied `verify-frida.mjs` imports `dist/domain/fridaRemoteAddress.js`, but the fixture creates a stub at `dist/contracts/fridaRemoteAddress.js`; Node reports `ERR_MODULE_NOT_FOUND`. ### Reproduction On exact main base `d3ab0faf52a02ff5a618f3ed7beb608b78752abd`, run `npm run test:focused -- tests/boundary/process/providerVerifierCleanup.test.ts`. On macOS arm64 with Node 24.22.1, four Frida cases failed with that missing module; four JEB cases passed. The same failure appeared in Linux CI test shard 4 and portable tests on #8591. ### Expected behavior The fixture should resolve the verifier's real built address-validation dependency so the controlled provider and cleanup outcomes reach the assertions. Keep this as an orchestration test; it does not prove real Frida behavior. ### Impact and scope The failure blocks the affected CI runs and prevents these four tests from exercising their intended cleanup paths. This does not establish a production verifier or real Frida bug. ### REA version Base commit `d3ab0faf52a02ff5a618f3ed7beb608b78752abd`. ### Runtime and platform Node 24.22.1; macOS arm64 local reproduction and Linux CI. ### Target and artifact context Synthetic engine-facing fixture, no real provider target. ### Interface Test/CI. ### Earliest failure stage Fixture module loading before verification or cleanup. ### Relevant output or evidence `ERR_MODULE_NOT_FOUND: .../dist/domain/fridaRemoteAddress.js` imported from the fixture's `scripts/verify-frida.mjs`. See #8591 CI. ### Typed outcome or recovery expected Resolve actual verifier dependencies, retain primary and cleanup errors, and preserve JEB controls. Do not infer real-provider behavior from this fixture. ### Analysis or suspected cause The verifier imports the domain path while the test still writes an unused contracts-path stub. ### Additional context cc @gensokyo-dev @kaoru0822-kitauji @N0zoM1z0

bsakaguchi added the

bug

triage

labels

2026-11-01 21:13:03 +00:00

bsakaguchi closed this issue

2026-11-04 20:25:26 +00:00

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#6664

No description provided.

Rows
Columns