fatal runtime error: failed to initiate panic, error 2948493472
Unanswered
Axe posted this in #help-forum
AxeOP
> [beehive 8/8] RUN npm run build:
0.133
0.133 > beehive@0.1.0 build
0.133 > RUST_BACKTRACE=full next build
0.133
0.488 Attention: Next.js now collects completely anonymous telemetry regarding usage.
0.488 This information is used to shape Next.js' roadmap and prioritize features.
0.488 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
0.488 https://nextjs.org/telemetry
0.488
0.562 ▲ Next.js 15.1.6
0.562
0.592 Creating an optimized production build ...
6.845 thread '<unnamed>' panicked at crates/oxide/src/scanner/detect_sources.rs:117:78:
6.845 called `Option::unwrap()` on a `None` value
6.845 stack backtrace:
6.846 0: 0xffffadd4b388 - <unknown>
6.846 1: 0xffffadc726c0 - <unknown>
6.846 2: 0xffffadd29818 - <unknown>
6.846 3: 0xffffadd4f4a4 - <unknown>
...
6.846 12: 0xffffadd763f4 - <unknown>
6.846 13: 0xffffadd5fd4c - <unknown>
6.846 14: 0xffffadd56ac0 - <unknown>
6.853 15: 0xaaaadbe57d80 - _ZN6v8impl12_GLOBAL__N_123FunctionCallbackWrapper6InvokeERKN2v820FunctionCallbackInfoINS2_5ValueEEE
6.853 16: 0xaaaadc17f0b0 - _ZN2v88internal25FunctionCallbackArguments4CallENS0_15CallHandlerInfoE
6.853 17: 0xaaaadc17f650 - _ZN2v88internal12_GLOBAL__N_119HandleApiCallHelperILb0EEENS0_11MaybeHandleINS0_6ObjectEEEPNS0_7IsolateENS0_6HandleINS0_10HeapObjectEEENS8_INS0_20FunctionTemplateInfoEEENS8_IS4_EEPmi
6.853 18: 0xaaaadc17fda8 - _ZN2v88internal21Builtin_HandleApiCallEiPmPNS0_7IsolateE
6.853 19: 0xaaaadcbeb964 - Builtins_CEntry_Return1_ArgvOnStack_BuiltinExit
6.853 fatal runtime error: failed to initiate panic, error 2948493472
[+] Running 0/1rker exited with code: null and signal: SIGABRT
⠏ Service beehive Building 8.0s
failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 11 Reply
AxeOP
No clue whats going on here or where to begin. Tried commenting out all routes but still got the same issue so doesnt seem to be related to any specific route