internal error: entered unreachable code

[indirection42]

When I use chopsticks to run the runtime PoC of https://github.com/open-web3-stack/PVQ, got the following error.
Changing runtime-log-level from 5 to 4 resolves the issue. Unsure if this is a misconfiguration or a bug.

bunx @acala-network/chopsticks@latest --config poc/runtime/chopsticks.yml --genesis output/chainspec.json

    chopsticks::executor  TRACE: Calling Metadata_metadata
    chopsticks::executor  TRACE: Completed Metadata_metadata
    chopsticks::executor  TRACE: Calling Core_initialize_block
    chopsticks::executor  TRACE: Completed Core_initialize_block
    chopsticks::executor  TRACE: Calling BlockBuilder_apply_extrinsic

panicked at src/task.rs:356:42:
internal error: entered unreachable code: unexpected log level 5

Stack:

Error
at imports.wbg.__wbg_new_abda76e883ba8a5f (/private/tmp/bunx-501-@acala-network/chopsticks@latest/node_modules/@acala-network/chopsticks-executor/dist/cjs/chopsticks_executor.js:749:19)
at wasm://wasm/00bdbb8a:wasm-function[1234]:0x1ba647
at wasm://wasm/00bdbb8a:wasm-function[1421]:0x1c242a
at wasm://wasm/00bdbb8a:wasm-function[105]:0xb47d3
at wasm://wasm/00bdbb8a:wasm-function[497]:0x16e5c7
at wasm://wasm/00bdbb8a:wasm-function[1491]:0x1c326c
at __wbg_adapter_48 (/private/tmp/bunx-501-@acala-network/chopsticks@latest/node_modules/@acala-network/chopsticks-executor/dist/cjs/chopsticks_executor.js:419:10)
at real (/private/tmp/bunx-501-@acala-network/chopsticks@latest/node_modules/@acala-network/chopsticks-executor/dist/cjs/chopsticks_executor.js:401:22)
at node:internal/process/task_queues:140:7
at AsyncResource.runInAsyncScope (node:async_hooks:206:9)

[14:29:06.877] INFO (block-builder): poc-runtime building #1
app: "chopsticks"
number: 1
extrinsics: []
umpCount: 0

node:internal/event_target:1084
process.nextTick(() => { throw err; });
^
Error [RuntimeError]: unreachable
at wasm://wasm/00bdbb8a:wasm-function[1234]:0x1ba820
at wasm://wasm/00bdbb8a:wasm-function[1421]:0x1c242a
at wasm://wasm/00bdbb8a:wasm-function[105]:0xb47d3
at wasm://wasm/00bdbb8a:wasm-function[497]:0x16e5c7
at wasm://wasm/00bdbb8a:wasm-function[1491]:0x1c326c
at __wbg_adapter_48 (/private/tmp/bunx-501-@acala-network/chopsticks@latest/node_modules/@acala-network/chopsticks-executor/dist/cjs/chopsticks_executor.js:419:10)
at real (/private/tmp/bunx-501-@acala-network/chopsticks@latest/node_modules/@acala-network/chopsticks-executor/dist/cjs/chopsticks_executor.js:401:22)
at node:internal/process/task_queues:140:7
at AsyncResource.runInAsyncScope (node:async_hooks:206:9)
at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)

Node.js v21.1.0
make: *** [run] Error 1

[indirection42]

Changing runtime-log-level from 5 to 4 works.

[ermalkaleci]

substrate runtime logs start from 0..4, in this case your runtime is emitting log level 5

[indirection42]

substrate runtime logs start from 0..4, in this case your runtime is emitting log level 5

It works with runtime-log-level: 5 before I updating chain-spec-builder. So I'm curious why it's incompatible now.

[ermalkaleci]

something must have changed

[ermalkaleci]

LogLevel is the first argument and running testing (which is current behaviour) error = 0
https://github.com/paritytech/polkadot-sdk/blob/431e06839addf318d1c251ec50097c748d423073/substrate/primitives/runtime/src/runtime_logger.rs#L60
https://github.com/smol-dot/smoldot/blob/d446dd3a7038d9aaca847fe7c54aee64a12b78ce/lib/src/executor/host.rs#L2216

[ermalkaleci]

Apparently in wasm debug is zero
https://github.com/paritytech/polkadot-sdk/blob/431e06839addf318d1c251ec50097c748d423073/substrate/primitives/tracing/src/types.rs#L26