RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f81322:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f81322:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f81322:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f81322:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f81322:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f81322:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f81322:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f81322:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f81322:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f81322:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:1751466 ❯ exports#count-a wasm:/wasm/02f6bb66:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:1751466 ❯ exports#count-a wasm:/wasm/02f6bb66:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f6bb66:1:1751466 ❯ exports#count-a wasm:/wasm/02f6bb66:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/036049de:1:35359 ❯ null.<anonymous> wasm:/wasm/036049de:1:2186752 ❯ null.<anonymous> wasm:/wasm/036049de:1:2189600 ❯ null.<anonymous> wasm:/wasm/036049de:1:2350233 ❯ null.<anonymous> wasm:/wasm/036049de:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/036049de:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "smoke-default". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/036049de:1:35359 ❯ null.<anonymous> wasm:/wasm/036049de:1:2186752 ❯ null.<anonymous> wasm:/wasm/036049de:1:2189600 ❯ null.<anonymous> wasm:/wasm/036049de:1:2350233 ❯ null.<anonymous> wasm:/wasm/036049de:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/036049de:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "resource-floats". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/036049de:1:35359 ❯ null.<anonymous> wasm:/wasm/036049de:1:2186752 ❯ null.<anonymous> wasm:/wasm/036049de:1:2189600 ❯ null.<anonymous> wasm:/wasm/036049de:1:2350233 ❯ null.<anonymous> wasm:/wasm/036049de:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/036049de:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "rename-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/036049de:1:9172057 ❯ null.<anonymous> wasm:/wasm/036049de:1:1758529 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/036049de:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:508:28 ❯ MessagePort.<anonymous> node:internal/worker:331:53 ❯ MessagePort.[nodejs.internal.kHybridDispatch] node:internal/event_target:845:20 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f834ee:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f834ee:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f834ee:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f834ee:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f834ee:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f834ee:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f834ee:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f70382:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f70382:1:1751466 ❯ exports#count-a wasm:/wasm/02f70382:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f70382:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f70382:1:1751466 ❯ exports#count-a wasm:/wasm/02f70382:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f70382:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f70382:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f70382:1:1751466 ❯ exports#count-a wasm:/wasm/02f70382:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03602b92:1:35359 ❯ null.<anonymous> wasm:/wasm/03602b92:1:2186752 ❯ null.<anonymous> wasm:/wasm/03602b92:1:2189600 ❯ null.<anonymous> wasm:/wasm/03602b92:1:2350233 ❯ null.<anonymous> wasm:/wasm/03602b92:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03602b92:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "type-imports". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03602b92:1:35359 ❯ null.<anonymous> wasm:/wasm/03602b92:1:2186752 ❯ null.<anonymous> wasm:/wasm/03602b92:1:2189600 ❯ null.<anonymous> wasm:/wasm/03602b92:1:2350233 ❯ null.<anonymous> wasm:/wasm/03602b92:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03602b92:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "resource-import-and-export". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03602b92:1:35359 ❯ null.<anonymous> wasm:/wasm/03602b92:1:2186752 ❯ null.<anonymous> wasm:/wasm/03602b92:1:2189600 ❯ null.<anonymous> wasm:/wasm/03602b92:1:2350233 ❯ null.<anonymous> wasm:/wasm/03602b92:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03602b92:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "records". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/03602b92:1:9172057 ❯ null.<anonymous> wasm:/wasm/03602b92:1:1758529 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03602b92:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:509:20 ❯ MessagePort.<anonymous> node:internal/worker:358:14 ❯ MessagePort.[nodejs.internal.kHybridDispatch] node:internal/event_target:843:20 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f8883e:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f8883e:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f8883e:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f8883e:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f8883e:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f8883e:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f8883e:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f78056:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f78056:1:1751466 ❯ exports#count-a wasm:/wasm/02f78056:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f78056:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f78056:1:1751466 ❯ exports#count-a wasm:/wasm/02f78056:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f78056:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f78056:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f78056:1:1751466 ❯ exports#count-a wasm:/wasm/02f78056:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03607a7e:1:35359 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:2186752 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:2189600 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:2350233 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03607a7e:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "smoke-export". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03607a7e:1:35359 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:2186752 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:2189600 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:2350233 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03607a7e:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "resource-floats". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03607a7e:1:35359 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:2186752 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:2189600 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:2350233 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03607a7e:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "rename-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/03607a7e:1:9172057 ❯ null.<anonymous> wasm:/wasm/03607a7e:1:1758529 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03607a7e:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:509:20 ❯ MessagePort.<anonymous> node:internal/worker:358:14 ❯ MessagePort.[nodejs.internal.kHybridDispatch] node:internal/event_target:843:20 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03903302:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03903302:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03903302:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03903302:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03903302:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03903302:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03903302:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03903302:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03903302:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03903302:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03903302:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03903302:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03903302:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03903302:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03903302:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03903302:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03903302:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03903302:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03903302:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03903302:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03903302:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03903302:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03903302:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03903302:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f0196:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f0196:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f0196:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f0196:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f0196:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f0196:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f0196:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f0196:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f0196:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f0196:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f0196:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f0196:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f0196:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f0196:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f0196:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f0196:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f0196:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f0196:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f0196:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f0196:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f0196:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f0196:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f0196:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f0196:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f84842:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f84842:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f84842:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f84842:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f84842:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f84842:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f84842:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "small-anonymous". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f84842:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f84842:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f84842:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f84842:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f84842:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f84842:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f84842:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "resource-borrow-in-record". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f84842:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f84842:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f84842:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f84842:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f84842:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f84842:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f84842:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "missing-export". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03f84842:1:9852790 ❯ abort wasm:/wasm/starling-raw.wasm-03f84842:1:9852799 ❯ call wasm:/wasm/starling-raw.wasm-03f84842:1:1855671 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f84842:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:508:28 ❯ MessagePort.<anonymous> node:internal/worker:331:53 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f813a6:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f813a6:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f813a6:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f813a6:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f813a6:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f813a6:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f813a6:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:1751466 ❯ exports#count-a wasm:/wasm/02f6bb16:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:1751466 ❯ exports#count-a wasm:/wasm/02f6bb16:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f6bb16:1:1751466 ❯ exports#count-a wasm:/wasm/02f6bb16:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03604842:1:35359 ❯ null.<anonymous> wasm:/wasm/03604842:1:2186752 ❯ null.<anonymous> wasm:/wasm/03604842:1:2189600 ❯ null.<anonymous> wasm:/wasm/03604842:1:2350233 ❯ null.<anonymous> wasm:/wasm/03604842:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03604842:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "smoke-default". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03604842:1:35359 ❯ null.<anonymous> wasm:/wasm/03604842:1:2186752 ❯ null.<anonymous> wasm:/wasm/03604842:1:2189600 ❯ null.<anonymous> wasm:/wasm/03604842:1:2350233 ❯ null.<anonymous> wasm:/wasm/03604842:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03604842:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "resource-floats". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03604842:1:35359 ❯ null.<anonymous> wasm:/wasm/03604842:1:2186752 ❯ null.<anonymous> wasm:/wasm/03604842:1:2189600 ❯ null.<anonymous> wasm:/wasm/03604842:1:2350233 ❯ null.<anonymous> wasm:/wasm/03604842:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03604842:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "rename-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/03604842:1:9172057 ❯ null.<anonymous> wasm:/wasm/03604842:1:1758529 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03604842:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:509:20 ❯ MessagePort.<anonymous> node:internal/worker:358:14 ❯ MessagePort.[nodejs.internal.kHybridDispatch] node:internal/event_target:843:20 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-039011ea:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-039011ea:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-039011ea:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-039011ea:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-039011ea:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-039011ea:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-039011ea:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-039011ea:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-039011ea:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-039011ea:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-039011ea:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-039011ea:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-039011ea:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-039011ea:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-039011ea:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-039011ea:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-039011ea:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-039011ea:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-039011ea:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-039011ea:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-039011ea:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-039011ea:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-039011ea:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-039011ea:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038eb976:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038eb976:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038eb976:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038eb976:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038eb976:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038eb976:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038eb976:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038eb976:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038eb976:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038eb976:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038eb976:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038eb976:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038eb976:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038eb976:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038eb976:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038eb976:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038eb976:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038eb976:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038eb976:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038eb976:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038eb976:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038eb976:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038eb976:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038eb976:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f86572:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f86572:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f86572:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f86572:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f86572:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f86572:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f86572:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "small-anonymous". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f86572:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f86572:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f86572:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f86572:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f86572:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f86572:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f86572:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "resource-floats". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f86572:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f86572:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f86572:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f86572:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f86572:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f86572:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f86572:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "rename-interface". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03f86572:1:9852790 ❯ abort wasm:/wasm/starling-raw.wasm-03f86572:1:9852799 ❯ call wasm:/wasm/starling-raw.wasm-03f86572:1:1855671 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f86572:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:509:20 ❯ MessagePort.<anonymous> node:internal/worker:358:14 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03901182:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03901182:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03901182:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03901182:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03901182:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03901182:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03901182:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03901182:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03901182:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03901182:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03901182:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03901182:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03901182:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03901182:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03901182:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03901182:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03901182:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03901182:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03901182:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03901182:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03901182:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03901182:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03901182:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03901182:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038eb942:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038eb942:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038eb942:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038eb942:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038eb942:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038eb942:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038eb942:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038eb942:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038eb942:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038eb942:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038eb942:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038eb942:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038eb942:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038eb942:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038eb942:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038eb942:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038eb942:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038eb942:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038eb942:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038eb942:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038eb942:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038eb942:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038eb942:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038eb942:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f865e6:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f865e6:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f865e6:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f865e6:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f865e6:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f865e6:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f865e6:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "small-anonymous". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f865e6:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f865e6:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f865e6:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f865e6:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f865e6:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f865e6:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f865e6:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "resource-borrow-in-record". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f865e6:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f865e6:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f865e6:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f865e6:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f865e6:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f865e6:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f865e6:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "missing-export". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03f865e6:1:9852790 ❯ abort wasm:/wasm/starling-raw.wasm-03f865e6:1:9852799 ❯ call wasm:/wasm/starling-raw.wasm-03f865e6:1:1855671 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f865e6:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:508:28 ❯ MessagePort.<anonymous> node:internal/worker:331:53 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f888ca:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f888ca:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f888ca:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f888ca:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f888ca:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f888ca:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f888ca:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f77fee:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:1751466 ❯ exports#count-a wasm:/wasm/02f77fee:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f77fee:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:1751466 ❯ exports#count-a wasm:/wasm/02f77fee:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f77fee:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f77fee:1:1751466 ❯ exports#count-a wasm:/wasm/02f77fee:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03607a26:1:35359 ❯ null.<anonymous> wasm:/wasm/03607a26:1:2186752 ❯ null.<anonymous> wasm:/wasm/03607a26:1:2189600 ❯ null.<anonymous> wasm:/wasm/03607a26:1:2350233 ❯ null.<anonymous> wasm:/wasm/03607a26:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03607a26:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "resources". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03607a26:1:35359 ❯ null.<anonymous> wasm:/wasm/03607a26:1:2186752 ❯ null.<anonymous> wasm:/wasm/03607a26:1:2189600 ❯ null.<anonymous> wasm:/wasm/03607a26:1:2350233 ❯ null.<anonymous> wasm:/wasm/03607a26:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03607a26:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "resource-borrow-import". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03607a26:1:35359 ❯ null.<anonymous> wasm:/wasm/03607a26:1:2186752 ❯ null.<anonymous> wasm:/wasm/03607a26:1:2189600 ❯ null.<anonymous> wasm:/wasm/03607a26:1:2350233 ❯ null.<anonymous> wasm:/wasm/03607a26:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03607a26:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "many-arguments". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/03607a26:1:9172057 ❯ null.<anonymous> wasm:/wasm/03607a26:1:1758529 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03607a26:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:508:28 ❯ MessagePort.<anonymous> node:internal/worker:331:53 ❯ MessagePort.[nodejs.internal.kHybridDispatch] node:internal/event_target:845:20 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03908696:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03908696:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03908696:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03908696:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03908696:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03908696:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03908696:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03908696:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03908696:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03908696:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03908696:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03908696:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03908696:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03908696:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03908696:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03908696:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03908696:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03908696:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03908696:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03908696:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03908696:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03908696:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03908696:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03908696:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f7e12:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f7e12:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f7e12:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f7e12:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f7e12:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f7e12:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f7e12:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f7e12:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f7e12:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f7e12:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f7e12:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f7e12:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f7e12:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f7e12:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f7e12:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f7e12:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f7e12:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f7e12:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f7e12:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f7e12:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f7e12:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f7e12:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f7e12:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f7e12:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f8970a:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f8970a:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f8970a:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f8970a:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f8970a:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f8970a:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f8970a:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "resource-with-lists". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f8970a:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f8970a:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f8970a:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f8970a:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f8970a:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f8970a:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f8970a:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "resource-borrow-import". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f8970a:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f8970a:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f8970a:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f8970a:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f8970a:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f8970a:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f8970a:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "lists". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03f8970a:1:9852790 ❯ abort wasm:/wasm/starling-raw.wasm-03f8970a:1:9852799 ❯ call wasm:/wasm/starling-raw.wasm-03f8970a:1:1855671 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f8970a:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:509:20 ❯ MessagePort.<anonymous> node:internal/worker:358:14 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f83562:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f83562:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f83562:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f83562:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f83562:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f83562:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f83562:1:9168732 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2009973 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2007615 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2252677 ❯ null.<anonymous> wasm:/wasm/02f83562:1:2346415 ❯ null.<anonymous> wasm:/wasm/02f83562:1:1751637 ❯ local:char/chars#take-char wasm:/wasm/02f83562:1:9256115 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f703be:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f703be:1:1751466 ❯ exports#count-a wasm:/wasm/02f703be:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f703be:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f703be:1:1751466 ❯ exports#count-a wasm:/wasm/02f703be:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/02f703be:1:9168561 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2009802 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2007444 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2252506 ❯ null.<anonymous> wasm:/wasm/02f703be:1:2346244 ❯ null.<anonymous> wasm:/wasm/02f703be:1:1751466 ❯ exports#count-a wasm:/wasm/02f703be:1:9255881 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32 ❯ test/bindings.js:155:22

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03602b26:1:35359 ❯ null.<anonymous> wasm:/wasm/03602b26:1:2186752 ❯ null.<anonymous> wasm:/wasm/03602b26:1:2189600 ❯ null.<anonymous> wasm:/wasm/03602b26:1:2350233 ❯ null.<anonymous> wasm:/wasm/03602b26:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03602b26:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "resource-top-level". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03602b26:1:35359 ❯ null.<anonymous> wasm:/wasm/03602b26:1:2186752 ❯ null.<anonymous> wasm:/wasm/03602b26:1:2189600 ❯ null.<anonymous> wasm:/wasm/03602b26:1:2350233 ❯ null.<anonymous> wasm:/wasm/03602b26:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03602b26:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "resource-alias-redux". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/03602b26:1:35359 ❯ null.<anonymous> wasm:/wasm/03602b26:1:2186752 ❯ null.<anonymous> wasm:/wasm/03602b26:1:2189600 ❯ null.<anonymous> wasm:/wasm/03602b26:1:2350233 ❯ null.<anonymous> wasm:/wasm/03602b26:1:1755318 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03602b26:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 This error originated in "test/bindings.js" 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 "many-arguments". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/03602b26:1:9172057 ❯ null.<anonymous> wasm:/wasm/03602b26:1:1758529 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/03602b26:1:9263418 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:508:28 ❯ MessagePort.<anonymous> node:internal/worker:331:53 ❯ MessagePort.[nodejs.internal.kHybridDispatch] node:internal/event_target:845:20 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03903306:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03903306:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03903306:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03903306:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03903306:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03903306:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03903306:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03903306:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03903306:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03903306:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03903306:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03903306:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03903306:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03903306:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03903306:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03903306:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03903306:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-03903306:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-03903306:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-03903306:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-03903306:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03903306:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-03903306:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-03903306:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f0186:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f0186:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f0186:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f0186:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f0186:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f0186:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f0186:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f0186:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f0186:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f0186:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f0186:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f0186:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f0186:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f0186:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f0186:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f0186:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f0186:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f0186:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f0186:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f0186:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f0186:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f0186:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f0186:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f0186:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f846fa:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f846fa:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f846fa:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f846fa:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f846fa:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f846fa:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f846fa:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "resource-with-lists". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f846fa:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f846fa:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f846fa:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f846fa:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f846fa:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f846fa:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f846fa:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "resource-alias-redux". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f846fa:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f846fa:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f846fa:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f846fa:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f846fa:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f846fa:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f846fa:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "lists". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03f846fa:1:9852790 ❯ abort wasm:/wasm/starling-raw.wasm-03f846fa:1:9852799 ❯ call wasm:/wasm/starling-raw.wasm-03f846fa:1:1855671 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f846fa:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:509:20 ❯ MessagePort.<anonymous> node:internal/worker:358:14 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-0390867a:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-0390867a:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-0390867a:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-0390867a:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-0390867a:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-0390867a:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-0390867a:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-0390867a:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-0390867a:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-0390867a:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-0390867a:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-0390867a:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-0390867a:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-0390867a:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-0390867a:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-0390867a:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-0390867a:1:9848939 ❯ abort wasm:/wasm/starling-raw.wasm-0390867a:1:9848948 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-0390867a:1:2143756 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-0390867a:1:2140173 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-0390867a:1:2387102 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-0390867a:1:2401171 ❯ call wasm:/wasm/starling-raw.wasm-0390867a:1:1848694 ❯ local:char/chars#take-char wasm:/wasm/starling-raw.wasm-0390867a:1:9940566 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f7ee6:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f7ee6:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f7ee6:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f7ee6:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f7ee6:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f7ee6:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f7ee6:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f7ee6:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-038f7ee6:1:9848759 ❯ abort wasm:/wasm/starling-raw.wasm-038f7ee6:1:9848768 ❯ std::__2::__libcpp_verbose_abort(char const*, ...) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2143580 ❯ std::__2::__throw_system_error(int, char const*) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2139997 ❯ void std::__2::__print::__vprint_nonunicode[abi:nn210104]<void>(_IO_FILE*, std::__2::basic_string_view<char, std::__2::char_traits<char>>, std::__2::basic_format_args<std::__2::basic_format_context<std::__2::back_insert_iterator<std::__2::__format::__output_buffer<char>>, char>>, bool) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2386926 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-038f7ee6:1:2400995 ❯ call wasm:/wasm/starling-raw.wasm-038f7ee6:1:1848518 ❯ exports#count-a wasm:/wasm/starling-raw.wasm-038f7ee6:1:9940323 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f89712:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f89712:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f89712:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f89712:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f89712:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f89712:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f89712:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "resource-top-level". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f89712:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f89712:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f89712:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f89712:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f89712:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f89712:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f89712:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "resource-alias-redux". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/starling-raw.wasm-03f89712:1:44250 ❯ __wasi_proc_exit wasm:/wasm/starling-raw.wasm-03f89712:1:2334180 ❯ _Exit wasm:/wasm/starling-raw.wasm-03f89712:1:2334171 ❯ exit wasm:/wasm/starling-raw.wasm-03f89712:1:2338284 ❯ api::Engine::abort(char const*) wasm:/wasm/starling-raw.wasm-03f89712:1:2405026 ❯ call wasm:/wasm/starling-raw.wasm-03f89712:1:1852412 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f89712:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "many-arguments". 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.

RuntimeError: unreachable ❯ mozalloc_abort wasm:/wasm/starling-raw.wasm-03f89712:1:9852790 ❯ abort wasm:/wasm/starling-raw.wasm-03f89712:1:9852799 ❯ call wasm:/wasm/starling-raw.wasm-03f89712:1:1855671 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/starling-raw.wasm-03f89712:1:9948395 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:508:28 ❯ MessagePort.<anonymous> node:internal/worker:331:53 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/04441206:1:10678411 ❯ null.<anonymous> wasm:/wasm/04441206:1:10678420 ❯ null.<anonymous> wasm:/wasm/04441206:1:2540064 ❯ null.<anonymous> wasm:/wasm/04441206:1:2536397 ❯ null.<anonymous> wasm:/wasm/04441206:1:2793779 ❯ null.<anonymous> wasm:/wasm/04441206:1:2808575 ❯ null.<anonymous> wasm:/wasm/04441206:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/04441206:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/04441206:1:10678411 ❯ null.<anonymous> wasm:/wasm/04441206:1:10678420 ❯ null.<anonymous> wasm:/wasm/04441206:1:2540064 ❯ null.<anonymous> wasm:/wasm/04441206:1:2536397 ❯ null.<anonymous> wasm:/wasm/04441206:1:2793779 ❯ null.<anonymous> wasm:/wasm/04441206:1:2808575 ❯ null.<anonymous> wasm:/wasm/04441206:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/04441206:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

Error: Failed to initialize component (weval (/Users/runner/work/ComponentizeJS/ComponentizeJS/node_modules/@bytecodealliance/weval/aarch64-macos/weval)): Process was killed by signal: SIGKILL ❯ componentize src/componentize.js:365:11 ❯ test/bindings.js:75:40

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043dbdea:1:10678083 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:10678092 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2539746 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2536079 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2793461 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2808257 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2233687 ❯ exports#count-a wasm:/wasm/043dbdea:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043dbdea:1:10678083 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:10678092 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2539746 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2536079 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2793461 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2808257 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2233687 ❯ exports#count-a wasm:/wasm/043dbdea:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043dbdea:1:10678083 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:10678092 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2539746 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2536079 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2793461 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2808257 ❯ null.<anonymous> wasm:/wasm/043dbdea:1:2233687 ❯ exports#count-a wasm:/wasm/043dbdea:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/0586177a:1:129724 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2742891 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2742882 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2747271 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2816584 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/0586177a:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "resource-alias". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/0586177a:1:129724 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2742891 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2742882 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2747271 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2816584 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/0586177a:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "missing-export". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/0586177a:1:129724 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2742891 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2742882 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2747271 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2816584 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/0586177a:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "keywords". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/0586177a:1:10687429 ❯ null.<anonymous> wasm:/wasm/0586177a:1:10687438 ❯ null.<anonymous> wasm:/wasm/0586177a:1:2245402 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/0586177a:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:509:20 ❯ MessagePort.<anonymous> node:internal/worker:358:14 This error originated in "test/bindings.js" 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 "http-server". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/04441186:1:10678411 ❯ null.<anonymous> wasm:/wasm/04441186:1:10678420 ❯ null.<anonymous> wasm:/wasm/04441186:1:2540064 ❯ null.<anonymous> wasm:/wasm/04441186:1:2536397 ❯ null.<anonymous> wasm:/wasm/04441186:1:2793779 ❯ null.<anonymous> wasm:/wasm/04441186:1:2808575 ❯ null.<anonymous> wasm:/wasm/04441186:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/04441186:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/04441186:1:10678411 ❯ null.<anonymous> wasm:/wasm/04441186:1:10678420 ❯ null.<anonymous> wasm:/wasm/04441186:1:2540064 ❯ null.<anonymous> wasm:/wasm/04441186:1:2536397 ❯ null.<anonymous> wasm:/wasm/04441186:1:2793779 ❯ null.<anonymous> wasm:/wasm/04441186:1:2808575 ❯ null.<anonymous> wasm:/wasm/04441186:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/04441186:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/04441186:1:10678411 ❯ null.<anonymous> wasm:/wasm/04441186:1:10678420 ❯ null.<anonymous> wasm:/wasm/04441186:1:2540064 ❯ null.<anonymous> wasm:/wasm/04441186:1:2536397 ❯ null.<anonymous> wasm:/wasm/04441186:1:2793779 ❯ null.<anonymous> wasm:/wasm/04441186:1:2808575 ❯ null.<anonymous> wasm:/wasm/04441186:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/04441186:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043dbe56:1:10678083 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:10678092 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2539746 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2536079 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2793461 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2808257 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2233687 ❯ exports#count-a wasm:/wasm/043dbe56:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043dbe56:1:10678083 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:10678092 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2539746 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2536079 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2793461 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2808257 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2233687 ❯ exports#count-a wasm:/wasm/043dbe56:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043dbe56:1:10678083 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:10678092 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2539746 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2536079 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2793461 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2808257 ❯ null.<anonymous> wasm:/wasm/043dbe56:1:2233687 ❯ exports#count-a wasm:/wasm/043dbe56:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/0586175e:1:129724 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2742891 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2742882 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2747271 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2816584 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/0586175e:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "rename-interface". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/0586175e:1:129724 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2742891 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2742882 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2747271 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2816584 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/0586175e:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "records". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/0586175e:1:129724 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2742891 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2742882 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2747271 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2816584 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/0586175e:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "kebab-fn-impt". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/0586175e:1:10687429 ❯ null.<anonymous> wasm:/wasm/0586175e:1:10687438 ❯ null.<anonymous> wasm:/wasm/0586175e:1:2245402 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/0586175e:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:508:28 ❯ MessagePort.<anonymous> node:internal/worker:331:53 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/04443a36:1:10678411 ❯ null.<anonymous> wasm:/wasm/04443a36:1:10678420 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2540064 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2536397 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2793779 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2808575 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/04443a36:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/04443a36:1:10678411 ❯ null.<anonymous> wasm:/wasm/04443a36:1:10678420 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2540064 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2536397 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2793779 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2808575 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/04443a36:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/04443a36:1:10678411 ❯ null.<anonymous> wasm:/wasm/04443a36:1:10678420 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2540064 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2536397 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2793779 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2808575 ❯ null.<anonymous> wasm:/wasm/04443a36:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/04443a36:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043db9aa:1:10678083 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:10678092 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2539746 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2536079 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2793461 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2808257 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2233687 ❯ exports#count-a wasm:/wasm/043db9aa:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043db9aa:1:10678083 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:10678092 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2539746 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2536079 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2793461 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2808257 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2233687 ❯ exports#count-a wasm:/wasm/043db9aa:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043db9aa:1:10678083 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:10678092 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2539746 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2536079 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2793461 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2808257 ❯ null.<anonymous> wasm:/wasm/043db9aa:1:2233687 ❯ exports#count-a wasm:/wasm/043db9aa:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/05853246:1:129724 ❯ null.<anonymous> wasm:/wasm/05853246:1:2742891 ❯ null.<anonymous> wasm:/wasm/05853246:1:2742882 ❯ null.<anonymous> wasm:/wasm/05853246:1:2747271 ❯ null.<anonymous> wasm:/wasm/05853246:1:2816584 ❯ null.<anonymous> wasm:/wasm/05853246:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05853246:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "rename-interface". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/05853246:1:129724 ❯ null.<anonymous> wasm:/wasm/05853246:1:2742891 ❯ null.<anonymous> wasm:/wasm/05853246:1:2742882 ❯ null.<anonymous> wasm:/wasm/05853246:1:2747271 ❯ null.<anonymous> wasm:/wasm/05853246:1:2816584 ❯ null.<anonymous> wasm:/wasm/05853246:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05853246:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "lists". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/05853246:1:129724 ❯ null.<anonymous> wasm:/wasm/05853246:1:2742891 ❯ null.<anonymous> wasm:/wasm/05853246:1:2742882 ❯ null.<anonymous> wasm:/wasm/05853246:1:2747271 ❯ null.<anonymous> wasm:/wasm/05853246:1:2816584 ❯ null.<anonymous> wasm:/wasm/05853246:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05853246:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "integers". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/05853246:1:10687429 ❯ null.<anonymous> wasm:/wasm/05853246:1:10687438 ❯ null.<anonymous> wasm:/wasm/05853246:1:2245402 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05853246:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:508:28 ❯ MessagePort.<anonymous> node:internal/worker:331:53 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/04443a1a:1:10678411 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:10678420 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2540064 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2536397 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2793779 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2808575 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/04443a1a:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/04443a1a:1:10678411 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:10678420 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2540064 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2536397 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2793779 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2808575 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/04443a1a:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/04443a1a:1:10678411 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:10678420 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2540064 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2536397 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2793779 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2808575 ❯ null.<anonymous> wasm:/wasm/04443a1a:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/04443a1a:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043dba66:1:10678083 ❯ null.<anonymous> wasm:/wasm/043dba66:1:10678092 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2539746 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2536079 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2793461 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2808257 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2233687 ❯ exports#count-a wasm:/wasm/043dba66:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043dba66:1:10678083 ❯ null.<anonymous> wasm:/wasm/043dba66:1:10678092 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2539746 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2536079 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2793461 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2808257 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2233687 ❯ exports#count-a wasm:/wasm/043dba66:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043dba66:1:10678083 ❯ null.<anonymous> wasm:/wasm/043dba66:1:10678092 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2539746 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2536079 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2793461 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2808257 ❯ null.<anonymous> wasm:/wasm/043dba66:1:2233687 ❯ exports#count-a wasm:/wasm/043dba66:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/058531ca:1:129724 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2742891 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2742882 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2747271 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2816584 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/058531ca:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "rename-interface". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/058531ca:1:129724 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2742891 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2742882 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2747271 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2816584 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/058531ca:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "lists". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/058531ca:1:129724 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2742891 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2742882 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2747271 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2816584 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/058531ca:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "integers". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/058531ca:1:10687429 ❯ null.<anonymous> wasm:/wasm/058531ca:1:10687438 ❯ null.<anonymous> wasm:/wasm/058531ca:1:2245402 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/058531ca:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:509:20 ❯ MessagePort.<anonymous> node:internal/worker:358:14 This error originated in "test/bindings.js" 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 "import-duplicated-interface". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/044475e2:1:10678411 ❯ null.<anonymous> wasm:/wasm/044475e2:1:10678420 ❯ null.<anonymous> wasm:/wasm/044475e2:1:2540064 ❯ null.<anonymous> wasm:/wasm/044475e2:1:2536397 ❯ null.<anonymous> wasm:/wasm/044475e2:1:2793779 ❯ null.<anonymous> wasm:/wasm/044475e2:1:2808575 ❯ null.<anonymous> wasm:/wasm/044475e2:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/044475e2:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

Error: Test timed out in 240000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/bindings.js:20:10

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:10678083 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:10678092 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2539746 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2536079 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2793461 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2808257 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2233687 ❯ exports#count-a wasm:/wasm/043d9d1e:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:10678083 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:10678092 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2539746 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2536079 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2793461 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2808257 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2233687 ❯ exports#count-a wasm:/wasm/043d9d1e:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:10678083 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:10678092 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2539746 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2536079 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2793461 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2808257 ❯ null.<anonymous> wasm:/wasm/043d9d1e:1:2233687 ❯ exports#count-a wasm:/wasm/043d9d1e:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

Error: Test timed out in 240000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/bindings.js:20:10

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/05856592:1:129724 ❯ null.<anonymous> wasm:/wasm/05856592:1:2742891 ❯ null.<anonymous> wasm:/wasm/05856592:1:2742882 ❯ null.<anonymous> wasm:/wasm/05856592:1:2747271 ❯ null.<anonymous> wasm:/wasm/05856592:1:2816584 ❯ null.<anonymous> wasm:/wasm/05856592:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05856592:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "resource-aggregates". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/05856592:1:129724 ❯ null.<anonymous> wasm:/wasm/05856592:1:2742891 ❯ null.<anonymous> wasm:/wasm/05856592:1:2742882 ❯ null.<anonymous> wasm:/wasm/05856592:1:2747271 ❯ null.<anonymous> wasm:/wasm/05856592:1:2816584 ❯ null.<anonymous> wasm:/wasm/05856592:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05856592:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "records". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/05856592:1:129724 ❯ null.<anonymous> wasm:/wasm/05856592:1:2742891 ❯ null.<anonymous> wasm:/wasm/05856592:1:2742882 ❯ null.<anonymous> wasm:/wasm/05856592:1:2747271 ❯ null.<anonymous> wasm:/wasm/05856592:1:2816584 ❯ null.<anonymous> wasm:/wasm/05856592:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05856592:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "kebab-fn-impt". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/05856592:1:10687429 ❯ null.<anonymous> wasm:/wasm/05856592:1:10687438 ❯ null.<anonymous> wasm:/wasm/05856592:1:2245402 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05856592:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:508:28 ❯ MessagePort.<anonymous> node:internal/worker:331:53 This error originated in "test/bindings.js" 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 "kebab-fn-impt". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/044464c6:1:10678411 ❯ null.<anonymous> wasm:/wasm/044464c6:1:10678420 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2540064 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2536397 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2793779 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2808575 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/044464c6:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/044464c6:1:10678411 ❯ null.<anonymous> wasm:/wasm/044464c6:1:10678420 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2540064 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2536397 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2793779 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2808575 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/044464c6:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/044464c6:1:10678411 ❯ null.<anonymous> wasm:/wasm/044464c6:1:10678420 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2540064 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2536397 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2793779 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2808575 ❯ null.<anonymous> wasm:/wasm/044464c6:1:2234005 ❯ local:char/chars#take-char wasm:/wasm/044464c6:1:10774152 ❯ Object.takeChar$1 [as takeChar] test/output/char/char.js:4165:3 ❯ Module.test test/cases/char/test.js:4:18

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043d9d26:1:10678083 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:10678092 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2539746 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2536079 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2793461 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2808257 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2233687 ❯ exports#count-a wasm:/wasm/043d9d26:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043d9d26:1:10678083 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:10678092 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2539746 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2536079 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2793461 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2808257 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2233687 ❯ exports#count-a wasm:/wasm/043d9d26:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/043d9d26:1:10678083 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:10678092 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2539746 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2536079 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2793461 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2808257 ❯ null.<anonymous> wasm:/wasm/043d9d26:1:2233687 ❯ exports#count-a wasm:/wasm/043d9d26:1:10773761 ❯ Object.countA test/output/args/args.js:4105:15 ❯ Module.test test/cases/args/test.js:4:32

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/05856562:1:129724 ❯ null.<anonymous> wasm:/wasm/05856562:1:2742891 ❯ null.<anonymous> wasm:/wasm/05856562:1:2742882 ❯ null.<anonymous> wasm:/wasm/05856562:1:2747271 ❯ null.<anonymous> wasm:/wasm/05856562:1:2816584 ❯ null.<anonymous> wasm:/wasm/05856562:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05856562:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "repeated-calls". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/05856562:1:129724 ❯ null.<anonymous> wasm:/wasm/05856562:1:2742891 ❯ null.<anonymous> wasm:/wasm/05856562:1:2742882 ❯ null.<anonymous> wasm:/wasm/05856562:1:2747271 ❯ null.<anonymous> wasm:/wasm/05856562:1:2816584 ❯ null.<anonymous> wasm:/wasm/05856562:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05856562:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "missing-export". 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.

RuntimeError: unreachable ❯ proc_exit wasm:/wasm/05856562:1:129724 ❯ null.<anonymous> wasm:/wasm/05856562:1:2742891 ❯ null.<anonymous> wasm:/wasm/05856562:1:2742882 ❯ null.<anonymous> wasm:/wasm/05856562:1:2747271 ❯ null.<anonymous> wasm:/wasm/05856562:1:2816584 ❯ null.<anonymous> wasm:/wasm/05856562:1:2241865 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05856562:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 This error originated in "test/bindings.js" 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 "kebab-fn-impt". 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.

RuntimeError: unreachable ❯ null.<anonymous> wasm:/wasm/05856562:1:10687429 ❯ null.<anonymous> wasm:/wasm/05856562:1:10687438 ❯ null.<anonymous> wasm:/wasm/05856562:1:2245402 ❯ wasi:http/incoming-handler@0.2.10#handle wasm:/wasm/05856562:1:10787148 ❯ Object.handle$1 [as handle] test/output/http-server/http-server.js:9449:3 ❯ node_modules/@bytecodealliance/preview2-shim/lib/nodejs/http.js:768:33 ❯ node_modules/@bytecodealliance/preview2-shim/lib/io/worker-io.js:75:5 ❯ Worker.<anonymous> node_modules/@bytecodealliance/preview2-shim/lib/synckit/index.js:65:9 ❯ Worker.emit node:events:509:20 ❯ MessagePort.<anonymous> node:internal/worker:358:14 This error originated in "test/bindings.js" 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 "integers". 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.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026