Dashboardopencode-loreforceWasm init-needs-wasm respawn

forceWasm init-needs-wasm respawn

Category: architecture
Confidence: 1.00
ID: 01a0a99a-1bde-70bd-9fdb-2b77126909bc
Project ID: 6f4be9ff-ed84-4cca-a9e7-732a0b0b8677
Cross-project: No
Recalled in other projects: 0
Source session: 0IlNEZeIJziYPH1rR
Created: 2026-09-16 09:44:04
Updated: 2026-09-16 09:44:04

Content

Chose one fresh worker with sticky WorkerInitData.forceWasm=true over switching the existing worker because onnxruntime-node caches the module after reading __LORE_ORT_BINDING_PATH__; only a new module graph can recover from native model-load incompatibility. Reject/drop the pending request through canonical shouldPostPerRequestError handling before resubmission, ignore stale worker error/exit events, preserve forceWasm across OOM respawns, and treat a second init-needs-wasm as terminal initialization failure to prevent loops.

Move to: