fix(design): add --api-timeout flag, raise default 120s→300s for image-gen #1972
RagavRidaAnnotations
8 errors and 15 warnings
|
evals (llm-judge, test/skill-llm-eval.test.ts)
Process completed with exit code 1.
|
|
error: Could not resolve authentication method. Expected either apiKey or authToken to be set. Or for one of the "X-Api-Key" or "Authorization" headers to be explicitly omitted:
node_modules/@anthropic-ai/sdk/client.mjs#L114
at validateHeaders (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:114:19)
at buildHeaders (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:481:14)
at async buildRequest (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:443:39)
at async makeRequest (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:221:50)
|
|
error: Could not resolve authentication method. Expected either apiKey or authToken to be set. Or for one of the "X-Api-Key" or "Authorization" headers to be explicitly omitted:
node_modules/@anthropic-ai/sdk/client.mjs#L114
at validateHeaders (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:114:19)
at buildHeaders (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:481:14)
at async buildRequest (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:443:39)
at async makeRequest (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:221:50)
|
|
error: Could not resolve authentication method. Expected either apiKey or authToken to be set. Or for one of the "X-Api-Key" or "Authorization" headers to be explicitly omitted:
node_modules/@anthropic-ai/sdk/client.mjs#L114
at validateHeaders (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:114:19)
at buildHeaders (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:481:14)
at async buildRequest (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:443:39)
at async makeRequest (/__w/gstack/gstack/node_modules/@anthropic-ai/sdk/client.mjs:221:50)
|
|
evals (e2e-workflow, test/skill-e2e-workflow.test.ts)
Process completed with exit code 1.
|
|
error: expect(received).toContain(expected):
test/skill-e2e-workflow.test.ts#L109
Expected to contain: "error_api"
Received: [ "success", "error_max_turns" ]
at <anonymous> (/__w/gstack/gstack/test/skill-e2e-workflow.test.ts:109:44)
|
|
error: expect(received).toContain(expected):
test/skill-e2e-workflow.test.ts#L109
Expected to contain: "error_api"
Received: [ "success", "error_max_turns" ]
at <anonymous> (/__w/gstack/gstack/test/skill-e2e-workflow.test.ts:109:44)
|
|
error: expect(received).toContain(expected):
test/skill-e2e-workflow.test.ts#L109
Expected to contain: "error_api"
Received: [ "success", "error_max_turns" ]
at <anonymous> (/__w/gstack/gstack/test/skill-e2e-workflow.test.ts:109:44)
|
|
build-image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/login-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (e2e-browse, test/skill-e2e-bws.test.ts, ubicloud-standard-8)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (llm-judge, test/skill-llm-eval.test.ts)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (e2e-qa-workflow, test/skill-e2e-qa-workflow.test.ts)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (e2e-design, test/skill-e2e-design.test.ts)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (e2e-review, test/skill-e2e-review.test.ts)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (e2e-plan, test/skill-e2e-plan.test.ts)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (e2e-qa-bugs, test/skill-e2e-qa-bugs.test.ts)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (e2e-codex, test/codex-e2e.test.ts)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (e2e-codex, test/codex-e2e.test.ts)
No files were found with the provided path: ~/.gstack-dev/evals/*.json. No artifacts will be uploaded.
|
|
evals (e2e-deploy, test/skill-e2e-deploy.test.ts)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (e2e-gemini, test/gemini-e2e.test.ts)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (e2e-gemini, test/gemini-e2e.test.ts)
No files were found with the provided path: ~/.gstack-dev/evals/*.json. No artifacts will be uploaded.
|
|
evals (e2e-routing, test/skill-routing-e2e.test.ts)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
evals (e2e-workflow, test/skill-e2e-workflow.test.ts)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
eval-e2e-browse
|
410 Bytes |
sha256:3a4fbf20d22dd56a667da916523b9077c8819acff17800132d7e350444d233fc
|
|
|
eval-e2e-deploy
|
411 Bytes |
sha256:f5cbfb1b4ef97bac1b2a47b07743d6468f5a84cc51ca9bc02a3dcca27ba28511
|
|
|
eval-e2e-design
|
410 Bytes |
sha256:01c0aeb16dceceaf6c6eddd0a440d107ea8bb0c248e320d47dd3fd62a1ad2889
|
|
|
eval-e2e-plan
|
405 Bytes |
sha256:9494ef8c8f880da8ae3bb0f3bfc5d89c3a03c641d4eeb70c9866179a47a6ca15
|
|
|
eval-e2e-qa-bugs
|
413 Bytes |
sha256:85638d92fad10fa0167a8b67f682dd7c69c900a5686ec5d77cc26ab390457224
|
|
|
eval-e2e-qa-workflow
|
426 Bytes |
sha256:39d2be98f824eedafde3e5ddf03da0975540578b7b9f730caa4cab073111457b
|
|
|
eval-e2e-review
|
411 Bytes |
sha256:15eb42808b4fb5973d32ff3e7a5d103513a00a3f1f4d8f2acdd4c1740bd94a18
|
|
|
eval-e2e-routing
|
414 Bytes |
sha256:83cf50b50e2c59f48f5f99aec86929a0974c33f6704f77b77d12080a3185375f
|
|
|
eval-e2e-workflow
|
4.49 KB |
sha256:176ead4a29ed47de9f00469d67c8aa1dcc245fc100367e66ac0df0e6ceb49071
|
|
|
eval-llm-judge
|
411 Bytes |
sha256:5168934b45b7778f5461797840bf804de45ab6551a87f2d440fe107f406e883b
|
|