Process completed with exit code 1.

Error: Request timed out after 30s ❯ Timeout._onTimeout packages/proxy/utils/tests.ts:212:14 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/proxy/src/providers/google.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 "should handle multi-turn with generated image via callProxyV1". 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.

Error: Request timed out after 30s ❯ Timeout._onTimeout packages/proxy/utils/tests.ts:212:14 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/proxy/src/providers/google.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 "should handle mixed text and image in response via callProxyV1". 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.

Error: Request timed out after 30s ❯ Timeout._onTimeout packages/proxy/utils/tests.ts:212:14 ❯ listOnTimeout node:internal/timers:581:17 ❯ processTimers node:internal/timers:519:7 This error originated in "packages/proxy/src/providers/google.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 "should handle inlineData (image) in response via callProxyV1". 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/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/