Process completed with exit code 1.

Error: Unexpected message from Worker: { taskId: 10036, result: undefined, error: null, usedMemory: 6791096 } ❯ WorkerInfo.onMessage dist/index.js:522:17 ❯ WorkerInfo._handleResponse dist/index.js:415:8 ❯ MessagePort.<anonymous> dist/index.js:370:45 ❯ MessagePort.[nodejs.internal.kHybridDispatch] node:internal/event_target:827:20 ❯ MessagePort.<anonymous> node:internal/per_context/messageport:23:28 This error originated in "test/uncaught-exception-from-handler.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "no named handler found from worker". 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.

The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520

The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520

The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677