Skip to content

Stop creating organizations in v1; send org-less sessions to v2 #6404

Stop creating organizations in v1; send org-less sessions to v2

Stop creating organizations in v1; send org-less sessions to v2 #6404

Triggered via pull request November 5, 2026 04:43
Status Failure
Total duration 3m 54s
Artifacts –

ci.yml

on: pull_request
Changed paths
7s
Changed paths
Matrix: e2e
Cloud evaluated closure
51s
Cloud evaluated closure
Desktop smoke build
55s
Desktop smoke build
Self-host Docker image
1m 44s
Self-host Docker image
Fit to window
Zoom out
Zoom in

Annotations

152 errors and 76 warnings
E2E (cloud 2of16)
Process completed with exit code 1.
[cloud] scenarios/artifact-approval.test.ts > Artifacts · declining an artifact action leaves it unrun: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
E2E (cloud 4of16)
Process completed with exit code 1.
[cloud] scenarios/google-health-checks.test.ts > Google · Calendar and Gmail catalog health checks run against the emulator: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/health-checks-ui.test.ts > Health checks (UI) · the combobox list scrolls inside the edit sheet: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-client-sessions.test.ts > MCP sessions · an unknown session id fails fast with a clean error, not a hang: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-client-sessions.test.ts > MCP sessions · a resumed session after idle runtime disposal restores cleanly: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-client-sessions.test.ts > MCP sessions · a second client resuming the session id continues the session: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-client-sessions.test.ts > MCP sessions · a real MCP client connects, lists tools, and executes code: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/auth-evidence.test.ts > Authentication · successful login exports diagnostics without its credentials: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/auth-evidence.test.ts > Authentication · valid credentials work in headers but not query parameters: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
E2E (cloud 3of16)
Process completed with exit code 1.
[cloud] cloud/mcp-sse-replay.test.ts > MCP streamable HTTP · in-flight call survives the session idle timeout: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-sse-replay.test.ts > MCP streamable HTTP · Last-Event-ID recovery stays scoped to its originating request: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-sse-replay.test.ts > MCP streamable HTTP · POST response abort is replayed on the next GET stream: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
Typecheck
Process completed with exit code 2.
Typecheck
@executor-js/cloud#typecheck: command (/home/runner/_work/executor/executor/apps/cloud) /home/runner/.bun/bin/bun run typecheck exited (2)
Typecheck
Module '"../extensions/billing/plans"' has no exported member 'shouldApplyFreeOrganizationLimit'.
Typecheck
Module '"../extensions/billing/plans"' has no exported member 'isOverFreeOrganizationLimit'.
Typecheck
'"../extensions/billing/plans"' has no exported member named 'hasPaidOrganizationSubscription'. Did you mean 'hasNonFreeOrganizationSubscription'?
Typecheck
Module '"../extensions/billing/plans"' has no exported member 'FREE_ORGANIZATIONS_PER_USER_LIMIT'.
[cloud] scenarios/artifacts.test.ts > Artifacts · a tweak updates the artifact in place, and a tweak that cannot render is refused: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/artifacts.test.ts > Artifacts · renaming and deleting in the console is what the agent sees next: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/api-tools.test.ts > API · a fresh identity starts with zero connections: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/api-tools.test.ts > API · typed client lists the available tools: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/session-gate.test.ts > Session gate · an org-less session is sent to onboarding before the app shell exists: e2e/cloud/session-gate.test.ts#L101
AssertionError: …onboarding owns this session: expected 'https://app.executor.sh/login?mode=si…' to be '/create-org' // Object.is equality Expected: "/create-org" Received: "https://app.executor.sh/login?mode=signup" ❯ Array.<anonymous> cloud/session-gate.test.ts:101:76 ❯ next ../node_modules/.bun/effect@4.0.0-beta.59/node_modules/effect/src/internal/effect.ts:1276:25 ❯ Object.~effect/Effect/evaluate ../node_modules/.bun/effect@4.0.0-beta.59/node_modules/effect/src/internal/core.ts:531:30 ❯ FiberImpl.runLoop ../node_modules/.bun/effect@4.0.0-beta.59/node_modules/effect/src/internal/effect.ts:633:39 ❯ runLoop ../node_modules/.bun/effect@4.0.0-beta.59/node_modules/effect/src/internal/effect.ts:593:22 ❯ evaluate ../node_modules/.bun/effect@4.0.0-beta.59/node_modules/effect/src/internal/effect.ts:1030:14 ❯ resume ../node_modules/.bun/effect@4.0.0-beta.59/node_modules/effect/src/internal/effect.ts:972:13
[cloud] cloud/session-gate.test.ts > Session gate · /cloud (the marketing CTA path) routes into the app: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/connect-panel.test.ts > Connect · the agent-connect panel gives working copy for both transports: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-protocol.test.ts > MCP protocol · a session cannot be ridden by a different account's bearer: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-protocol.test.ts > MCP protocol · a terminated session's id is rejected with a reconnect error: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-protocol.test.ts > MCP protocol · initialize opens a session and notifications are accepted with 202: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-protocol.test.ts > MCP protocol · verbs outside the MCP transport are rejected with a JSON-RPC 405: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-protocol.test.ts > MCP protocol · a non-org path segment is not claimed by the MCP route: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-protocol.test.ts > MCP protocol · the URL can pin the active org, but membership is enforced: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/execute-emit-envelope.test.ts > Execute · an emit-only script reports its emitted output in the result envelope: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/auth-session.test.ts > Auth · logout ends the AuthKit session upstream and tells the browser to drop the cookie: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/auth-session.test.ts > Auth · a completed login's session cookie authorizes the session API: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/connect-deep-link.test.ts > Connect · /connect/<slug> lands an end user in that integration's connect flow: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/toolkit-policy-perf.test.ts > Toolkits · connect time does not scale with catalog size: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/org-slug-foreign.test.ts > Org URLs · opening another of your orgs by slug works without switching the session: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/integrations-api.test.ts > Connections · org-shared and personal connections coexist with distinct tool addresses: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/integrations-api.test.ts > Integrations · a connected MCP server's tool executes through the execution surface: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-browser-resume-page.test.ts > MCP approval · browser resume page approves a paused execution through the UI: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/integrations-api.test.ts > Integrations · MCP addServer registers the catalog row without dialing the endpoint: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/integrations-api.test.ts > Integrations · a connected OpenAPI operation executes against the live upstream API: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/integrations-api.test.ts > Integrations · previewSpec reports summary metadata before anything is stored: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/frontend-error-reporting.test.ts > Frontend errors · a failed API request is reported without request data: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/integrations-api.test.ts > Integrations · an OpenAPI spec round-trips the catalog: add, fetch, update, remove: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/auth-hint.test.ts > Auth hint · logout clears the hint with the session: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/auth-hint.test.ts > Auth hint · the FIRST load on a fresh browser paints the real shell — the gate minted the hint: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/connection-owner-isolation.test.ts > Connections · the same account in two orgs gets two separate credential spaces: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/connection-owner-isolation.test.ts > Connections · an org-owned connection is shared with every member of the org: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/account-api.test.ts > Account · an API key is minted once, authorizes the API as a bearer, and can be revoked: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/account-api.test.ts > Account · /account/me reflects the signed-in user and their organization: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/health-checks-mcp.test.ts > Health checks · MCP liveness reports healthy, then expired when the token is revoked: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/artifact-source-roundtrip.test.ts > Artifacts · text-only clients read current source and edit the same artifact: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/artifact-loading-surface.test.ts > Artifacts · opening an artifact shows one loading surface, not three: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-execution-metering.test.ts > Billing · every MCP execution is metered to Autumn, one unit per run: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/admin-users.test.ts > Admin · one workspace's owner sees nothing of another workspace: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/admin-users.test.ts > Admin · the owner sees every member of the workspace and what each has connected: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
Test
Process completed with exit code 1.
[cloud] cloud/mcp-execution-limits.test.ts > Billing · a balance-check timeout fails open and still runs the execution: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/mcp-execution-limits.test.ts > Billing · a balance-check failure fails open and still runs the execution: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
src/account/organization-limits.node.test.ts > organization limits > does not treat inactive paid plans or free plans as paid: apps/cloud/src/account/organization-limits.node.test.ts#L21
TypeError: hasPaidOrganizationSubscription is not a function ❯ src/account/organization-limits.node.test.ts:21:12
[cloud] cloud/mcp-execution-limits.test.ts > Billing · an org out of executions is blocked before the code ever runs: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
src/account/organization-limits.node.test.ts > organization limits > treats active and trialing paid org subscriptions as paid: apps/cloud/src/account/organization-limits.node.test.ts#L13
TypeError: hasPaidOrganizationSubscription is not a function ❯ src/account/organization-limits.node.test.ts:13:12
[cloud] cloud/connections-credentials.test.ts > Connections · reading or removing an unknown connection fails with not-found: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
Test
@executor-js/cloud#test: command (/home/runner/_work/executor/executor/apps/cloud) /home/runner/.bun/bin/bun run test exited (1)
[cloud] cloud/connections-credentials.test.ts > Connections · a removed connection disappears from both list and get: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/admin-mfa-api.test.ts > Admin MFA API · restarting enrollment cannot reset the rate limit: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/admin-mfa-api.test.ts > Admin MFA API · requires same-origin requests and binds verification to the session: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/v2-moved-notice.test.ts > v2 moved · malformed move metadata shows no notice and keeps the import link: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/v2-moved-notice.test.ts > v2 moved · keeping v1 asks why, and sending the answer hides the notice: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/v2-moved-notice.test.ts > v2 moved · a moved org's dashboard says where it lives in v2, and ✕ hides it: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/repro-listener-supersede.test.ts > REGRESSION · a second standalone listener must not evict the first: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/org-delete.test.ts > Organizations · an admin deletes the organization from settings: e2e/cloud/org-delete.test.ts#L28
TimeoutError: locator.fill: Timeout 30000ms exceeded. Call log: - waiting for getByPlaceholder('Northwind Labs') ❯ cloud/org-delete.test.ts:28:55 ❯ step src/surfaces/browser.ts:276:15 ❯ cloud/org-delete.test.ts:26:7 ❯ src/surfaces/browser.ts:288:13
[cloud] cloud/integrations-refresh.test.ts > Integrations · a spec pasted as a blob is not refreshable (canRefresh): e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/integrations-refresh.test.ts > Integrations · a spec registered from a URL is refreshable (canRefresh): e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/billing-trial-checkout-stale.test.ts > Billing · completing the trial checkout shows the new plan without a reload: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/connection-setup-ux.test.ts > Slack OAuth · provider consent saves a connection: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/org-limit.test.ts > Billing · the free plan stops organization creation after 3: e2e/cloud/org-limit.test.ts#L28
TimeoutError: locator.waitFor: Timeout 30000ms exceeded. Call log: - waiting for getByPlaceholder('Northwind Labs') to be visible ❯ cloud/org-limit.test.ts:28:55 ❯ step src/surfaces/browser.ts:276:15 ❯ cloud/org-limit.test.ts:26:7 ❯ src/surfaces/browser.ts:288:13
[cloud] cloud/billing-customer-provisioning.test.ts > Billing · an unrelated billing failure is reported, not retried away: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/billing-customer-provisioning.test.ts > Billing · creating an organization provisions it as a billing customer: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/auth-methods.test.ts > Auth methods · a no-auth MCP server can declare an API key method later: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/auth-methods.test.ts > Auth methods · adding an API key method keeps a detected OAuth method: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] scenarios/auth-methods.test.ts > Auth methods · an MCP server can declare OAuth and an API key side by side: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/tenant-isolation.test.ts > Tenant isolation · the same integration slug in two orgs is two independent records: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/onboarding-mcp-url.test.ts > Onboarding · the MCP setup step hands the user their org-scoped MCP server URL: e2e/cloud/onboarding-mcp-url.test.ts#L25
TimeoutError: locator.waitFor: Timeout 30000ms exceeded. Call log: - waiting for getByPlaceholder('Northwind Labs') to be visible ❯ cloud/onboarding-mcp-url.test.ts:25:57 ❯ step src/surfaces/browser.ts:276:15 ❯ cloud/onboarding-mcp-url.test.ts:20:7 ❯ src/surfaces/browser.ts:288:13
[cloud] cloud/auth-routing-flow.test.ts > Auth routing · signed out → login → onboarding → dashboard, one browser session: e2e/cloud/auth-routing-flow.test.ts#L55
TimeoutError: page.waitForURL: Timeout 30000ms exceeded. =========================== logs =========================== waiting for navigation until "load" navigated to "https://app.executor.sh/login?mode=signup" ============================================================ ❯ cloud/auth-routing-flow.test.ts:55:20 ❯ step src/surfaces/browser.ts:276:15 ❯ cloud/auth-routing-flow.test.ts:49:7 ❯ src/surfaces/browser.ts:288:13
[cloud] cloud/org-switcher.test.ts > Organizations · switching organizations switches the workspace: e2e/cloud/org-switcher.test.ts#L25
TimeoutError: locator.waitFor: Timeout 30000ms exceeded. Call log: - waiting for getByPlaceholder('Northwind Labs') to be visible ❯ cloud/org-switcher.test.ts:25:55 ❯ step src/surfaces/browser.ts:276:15 ❯ cloud/org-switcher.test.ts:23:7 ❯ src/surfaces/browser.ts:288:13
[cloud] cloud/logout-stale-session.test.ts > Sign-out · a second open tab signs out too instead of showing raw JSON: e2e/targets/cloud.ts#L93
Error: cloud newIdentity: create-organization failed (410) ❯ targets/cloud.ts:93:17
[cloud] cloud/login-csrf.test.ts > Auth · a provider-initiated login restarts with browser-bound state: e2e/cloud/login-csrf.test.ts#L116
TimeoutError: page.waitForURL: Timeout 30000ms exceeded. =========================== logs =========================== waiting for navigation until "load" navigated to "https://app.executor.sh/login?mode=signup" ============================================================ ❯ cloud/login-csrf.test.ts:116:20 ❯ step src/surfaces/browser.ts:276:15 ❯ cloud/login-csrf.test.ts:112:7 ❯ src/surfaces/browser.ts:288:13
[cloud] cloud/login-csrf.test.ts > Login CSRF · state is required, bound to the browser, and consumed after login: e2e/cloud/login-csrf.test.ts#L62
TimeoutError: page.waitForURL: Timeout 30000ms exceeded. =========================== logs =========================== waiting for navigation until "load" navigated to "https://app.executor.sh/login?mode=signup" ============================================================ ❯ cloud/login-csrf.test.ts:62:20 ❯ step src/surfaces/browser.ts:276:15 ❯ cloud/login-csrf.test.ts:59:7 ❯ src/surfaces/browser.ts:288:13
Changed paths
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, dorny/paths-filter@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Lint
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Format
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 2of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 4of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 1of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 10of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 3of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Typecheck
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Typecheck
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Typecheck
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Typecheck
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Typecheck
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Typecheck
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Typecheck
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Typecheck
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Typecheck
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Typecheck
The `catch` callback in `Effect.try` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Typecheck
The `catch` callback in `Effect.try` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
E2E (cloud 5of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 8of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 7of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 16of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 13of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (local 2of2)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Cloud evaluated closure
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Cloud evaluated closure
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Cloud evaluated closure
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Cloud evaluated closure
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Cloud evaluated closure
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Cloud evaluated closure
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Cloud evaluated closure
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Cloud evaluated closure
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Cloud evaluated closure
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Cloud evaluated closure
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Cloud evaluated closure
The `catch` callback in `Effect.try` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
E2E (local 1of2)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Desktop smoke build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
Desktop smoke build
The `catch` callback in `Effect.tryPromise` returns `unknown`, so the Effect error type stays untyped. A specific typed error preserves error-channel information, for example by narrowing the value or wrapping it in `Data.TaggedError`. effect(unknownInEffectCatch)
E2E (selfhost 2of10)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (selfhost 3of10)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 11of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 12of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 15of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 6of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (selfhost 7of10)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (selfhost 1of10)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (selfhost 10of10)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Self-host Docker image
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 9of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (selfhost 9of10)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (selfhost 5of10)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 14of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (selfhost 8of10)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (selfhost 6of10)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (selfhost 4of10)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/