feat: mainnet execution simulation #461
Annotations
4 errors
Run tests:
components/clarinet-sdk-wasm/pkg-node/clarinet_sdk.js#L1600
Error: recursive use of an object detected which would lead to unsafe aliasing in rust
❯ module.exports.__wbindgen_throw ../../clarinet-sdk-wasm/pkg-node/clarinet_sdk.js:1600:11
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:5315781
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:5315770
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:655469
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:3879392
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:4789771
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:4789757
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:4842984
❯ __wbg_adapter_48 ../../clarinet-sdk-wasm/pkg-node/clarinet_sdk.js:191:10
❯ real ../../clarinet-sdk-wasm/pkg-node/clarinet_sdk.js:176:20
This error originated in "tests/simnet-usage.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "can get_assets_maps". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Run tests:
components/clarinet-sdk-wasm/pkg-node/clarinet_sdk.js#L1600
Error: recursive use of an object detected which would lead to unsafe aliasing in rust
❯ module.exports.__wbindgen_throw ../../clarinet-sdk-wasm/pkg-node/clarinet_sdk.js:1600:11
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:5315781
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:5315770
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:655469
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:3879392
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:4789771
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:4789757
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:4842984
❯ __wbg_adapter_48 ../../clarinet-sdk-wasm/pkg-node/clarinet_sdk.js:191:10
❯ real ../../clarinet-sdk-wasm/pkg-node/clarinet_sdk.js:176:20
This error originated in "tests/simnet-usage.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "handle invalid project". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Run tests:
components/clarinet-sdk-wasm/pkg-node/clarinet_sdk.js#L777
RuntimeError: unreachable
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:4447070
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:4703234
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:4516798
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:2691951
❯ null.<anonymous> wasm:/wasm/01e5cc72:1:4784120
❯ Proxy.executeCommand ../../clarinet-sdk-wasm/pkg-node/clarinet_sdk.js:777:30
❯ tests/simnet-usage.test.ts:415:27
|
Run tests
Process completed with exit code 1.
|
Loading