feat(api): publish the typed remote client #5582
m-mohamedci.yml
on: pull_request
Changed paths
7s
Matrix: e2e
Cloud evaluated closure
53s
Desktop smoke build
46s
Self-host Docker image
35s
Annotations
136 errors and 67 warnings
|
Test
Process completed with exit code 1.
|
|
Test
@executor-js/cloudflare#test: command (/home/runner/_work/executor/executor/packages/hosts/cloudflare) /home/runner/.bun/bin/bun run test exited (1)
|
|
src/mcp/agent-session-model-resume.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../../core/api/src/handlers/executions.ts:6:1
❯ ../../core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
src/mcp/agent-session-durable-object.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../../core/api/src/handlers/executions.ts:6:1
❯ ../../core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
E2E (selfhost 2of10)
Process completed with exit code 1.
|
|
[selfhost] scenarios/health-checks-ui.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
Typecheck
'outcome' is of type 'unknown'.
|
|
Typecheck
'outcome' is of type 'unknown'.
|
|
Typecheck
'outcome' is of type 'unknown'.
|
|
Typecheck
Parameter 'id' implicitly has an 'any' type.
|
|
Typecheck
This Effect requires a service that is missing from the expected Effect context: `unknown`. effect(missingEffectContext)
|
|
Typecheck
Missing errors unknown in the expected Effect type. effect(missingEffectError)
|
|
Typecheck
Type 'Effect<any, unknown, unknown>' is not assignable to type 'Effect<string, ArtifactActionError, ExecutorService>'.
|
|
Typecheck
Cannot find module '@executor-js/host-mcp/tool-call-code' or its corresponding type declarations.
|
|
Typecheck
Cannot find module '@executor-js/host-mcp/artifact-action' or its corresponding type declarations.
|
|
Typecheck
Cannot find module '@executor-js/execution' or its corresponding type declarations.
|
|
E2E (selfhost 1of10)
Process completed with exit code 1.
|
|
[selfhost] scenarios/artifact-approval.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
E2E (cloud 2of16)
Process completed with exit code 1.
|
|
E2E (cloud 4of16)
Process completed with exit code 1.
|
|
E2E (cloud 16of16)
Process completed with exit code 1.
|
|
E2E (cloud 10of16)
Process completed with exit code 1.
|
|
[selfhost] scenarios/tool-call-contract.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/openapi-update-spec.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/oauth-setup-failure-cause.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/namespace-search-tools.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/microsoft-graph-full.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/mcp-cloudflare-codemode-warning.test.ts > MCP add flow · a Cloudflare URL without codemode=false gets the opt-out warning:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/mcp-catalog-sync-ui.test.ts > MCP catalog · the Tools tab follows a server-side rename after a list_changed notification:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/google-photos-preset-ui.test.ts > Google Photos products are separate registry cards with separate add flows:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/connection-health-verdict.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/artifact-loading-surface.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
E2E (cloud 12of16)
Process completed with exit code 1.
|
|
E2E (cloud 1of16)
Process completed with exit code 1.
|
|
E2E (cloud 9of16)
Process completed with exit code 1.
|
|
[selfhost] selfhost/connect-modal-credential-ux.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/provider-plugins-ui.test.ts > Google and Microsoft products are registry cards that resolve into prefilled add flows:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/policy-tool-approval.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/openapi-ndjson-output.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/oauth-refresh-rejected-non-json.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/metadata-editing.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/integrations-catalog-search.test.ts > Add page: a registry row adds in place, and falls back to the config screen:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/graphql-introspection-health.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/google-health-checks.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/docs-link.test.ts > Shell · the sidebar links to the docs from inside the app:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
E2E (cloud 8of16)
Process completed with exit code 1.
|
|
E2E (cloud 5of16)
Process completed with exit code 1.
|
|
[selfhost] selfhost/mcp-oauth-slow-connect.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/mcp-connect-card-url.test.ts > MCP · the URL printed by the Connect card is actually served:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/tools-contract.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/policies.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/openapi-integration.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
E2E (cloud 11of16)
Process completed with exit code 1.
|
|
[selfhost] scenarios/oauth-callback-url.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/health-checks.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/connection-remove-confirm.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/artifacts.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/artifact-preview-gallery.test.ts > Artifacts · the gallery shows each artifact's real layout, in light and dark:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
E2E (cloud 14of16)
Process completed with exit code 1.
|
|
E2E (cloud 3of16)
Process completed with exit code 1.
|
|
[selfhost] scenarios/microsoft-emulator.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/integrations.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/first-party-oauth.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/connect-handoff.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/auth-methods-ui.test.ts > Auth methods · the add flow declares an API key alongside the detected method:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/api-tools.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/toolkits-mcp.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/mcp-request-headers-add.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/mcp-oauth-cimd-connect.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/connection-duplicate-name-demo.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/mcp-oauth-reconnect-origin-drift.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/mcp-oauth-reconnect-health.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/mcp-approve.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/shape-memory.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/openapi-unknown-args.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/oauth-second-connection.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/namespace-enumeration.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/mcp-catalog-sync.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/connect-handoff-session.test.ts > Connect · developer session: agent chat → handoff link → paste key → verified send:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/browser-approval.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
E2E (cloud 6of16)
Process completed with exit code 1.
|
|
[selfhost] selfhost/api-keys-feedback.test.ts > API keys · the copy button copies a new key on a plain-HTTP self-host:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] selfhost/api-keys-feedback.test.ts > API keys · the page is reachable from the main sidebar:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] selfhost/admin-users-console.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/run-panel-auto-approve.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/openapi-server-selection.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/oauth-scope-insufficient.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/microsoft-graph-default.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/mcp-add-url-typing-probe.test.ts > MCP add flow · a half-typed Server URL is not probed:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/google-disabled-api.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/auth-methods.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/detected-auth-immutable-ui.test.ts > Detected auth · an MCP probe's OAuth method is immutable in the add flow:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] selfhost/auth-methods-ui.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/admin-users-pager.test.ts > Admin · the Users pager walks a workspace larger than one page without dropping or repeating anyone:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/policy-remove-confirm.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/policies-ui.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/openapi-multi-key-auth-ui.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/oauth-refresh-on-401.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/mcp-session-state.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/integration-families.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/dialog-outside-dismiss.test.ts > Dialogs (UI) · Outside click keeps a form open, closes a field-free confirm:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
E2E (cloud 7of16)
Process completed with exit code 1.
|
|
E2E (cloud 15of16)
Process completed with exit code 1.
|
|
E2E (cloud 13of16)
Process completed with exit code 1.
|
|
[selfhost] scenarios/org-slug-routing.test.ts > Org URLs · console paths carry the organization slug:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/openapi-add-integration-action-bar.test.ts > OpenAPI · Add integration commits the integration and the action bar is a single node:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
[selfhost] scenarios/no-auth-connection.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/mcp-execute.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/health-checks-mcp.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] scenarios/connect-deep-link.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/oauth-popup-callback-org-state.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/mcp-oauth-scope-discovery.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/mcp-browser-approval-ownership.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[selfhost] selfhost/cli-device-login.test.ts > CLI · executor login device flow → authenticated /api call:
e2e/targets/selfhost.ts#L40
Error: selfhost: sign-in set no cookie (500)
❯ signInSession targets/selfhost.ts:40:33
❯ targets/selfhost.ts:165:41
|
|
Self-host Docker image
buildx failed with: /src/solver/jobs.go:1182
|
|
Desktop smoke build
Process completed with exit code 1.
|
|
Cloud evaluated closure
Process completed with exit code 1.
|
|
E2E (local 2of2)
Process completed with exit code 1.
|
|
[local] local/toolkits-mcp.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[local] local/stdio-mcp.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[local] local/server-profile-header-env.test.ts > CLI server profiles · header env mappings are persisted without secret values:
e2e/local/server-profile-header-env.test.ts#L44
Error: executor server add cloudflare https://executor.example --header-env CF-Access-Client-Id=EXECUTOR_CF_ACCESS_CLIENT_ID --header-env CF-Access-Client-Secret=EXECUTOR_CF_ACCESS_CLIENT_SECRET --default failed with 1
error: Cannot find module '@executor-js/execution' from '/home/runner/_work/executor/executor/packages/core/api/src/server/execution-stack.ts'
Bun v1.3.11 (Linux x64)
❯ runCli local/server-profile-header-env.test.ts:44:11
❯ local/server-profile-header-env.test.ts:56:7
|
|
[local] local/oauth-await-longpoll.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[local] local/mcp-browser-approve.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[local] local/cli-call-logged-out.test.ts > CLI call · a signed-out hosted profile explains how to log back in:
e2e/local/cli-call-logged-out.test.ts#L113
Error: timed out waiting for visible terminal predicate
❯ Screen.waitUntil ../node_modules/.bun/@kitlangton+terminal-control@0.3.0+1929d4f7655cd21e/node_modules/@kitlangton/terminal-control/src/index.ts:591:40
❯ cli.session.cwd local/cli-call-logged-out.test.ts:113:28
❯ src/surfaces/cli.ts:100:26
|
|
[local] local/auth.test.ts > Local auth · opening the app without the token shows the gate; pasting it connects:
e2e/src/scenario.ts#L138
Error: Test timed out in 180000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ scenario src/scenario.ts:138:3
❯ local/auth.test.ts:53:1
|
|
[local] local/auth.test.ts > Local auth · the CLI's ?_token URL boots an authenticated console:
e2e/src/scenario.ts#L138
Error: Test timed out in 180000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ scenario src/scenario.ts:138:3
❯ local/auth.test.ts:23:1
|
|
[local] local/update-notice.test.ts > Local update · the desktop bridge shows a native restart-to-update card, not the npm command:
e2e/src/scenario.ts#L138
Error: Test timed out in 180000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ scenario src/scenario.ts:138:3
❯ local/update-notice.test.ts:112:1
|
|
[local] local/update-notice.test.ts > Local update · the web shell sidebar surfaces the update-available card:
e2e/src/scenario.ts#L138
Error: Test timed out in 180000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ scenario src/scenario.ts:138:3
❯ local/update-notice.test.ts:72:1
|
|
[local] local/update-notice.test.ts > Local update · the CLI ready banner nudges to upgrade when a newer version is published:
e2e/local/update-notice.test.ts#L46
Error: timed out waiting for visible terminal predicate
❯ Screen.waitUntil ../node_modules/.bun/@kitlangton+terminal-control@0.3.0+1929d4f7655cd21e/node_modules/@kitlangton/terminal-control/src/index.ts:591:40
❯ cli.session.cwd local/update-notice.test.ts:46:28
❯ src/surfaces/cli.ts:100:26
|
|
[local] local/stdio-mcp-edit-ui.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[local] local/oauth-token-durability.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[local] local/mcp-native-elicitation.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[local] local/codex-plugins.test.ts:
packages/core/api/src/handlers/executions.ts#L6
Error: Cannot find package '@executor-js/execution' imported from /home/runner/_work/executor/executor/packages/core/api/src/handlers/executions.ts
❯ ../packages/core/api/src/handlers/executions.ts:6:1
❯ ../packages/core/api/src/handlers/index.ts:7:1
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MODULE_NOT_FOUND' }
|
|
[local] local/cli-mcp-daemon-attach-stress.test.ts > Local CLI MCP · killing the daemon under load tears bridges down without hanging:
e2e/local/cli-mcp-daemon-attach-stress.test.ts#L75
Error: daemon stdout closed before ready: $ EXECUTOR_DEV=1 EXECUTOR_DATA_DIR=${EXECUTOR_DATA_DIR:-apps/local/.executor-dev} bun run apps/cli/src/main.ts daemon run --foreground --port "0" --hostname "127.0.0.1" --scope /home/runner/_work/executor/executor/apps/local
error: Cannot find module '@executor-js/execution' from '/home/runner/_work/executor/executor/packages/core/api/src/server/execution-stack.ts'
Bun v1.3.11 (Linux x64)
error: script "dev:cli" exited with code 1
❯ Socket.<anonymous> local/cli-mcp-daemon-attach-stress.test.ts:75:19
|
|
[local] local/cli-mcp-daemon-attach-stress.test.ts > Local CLI MCP · a cold-start race elects exactly one server and every client attaches:
e2e/local/cli-mcp-daemon-attach-stress.test.ts#L258
AssertionError: client #0 lost the race: MCP error -32000: Connection closed
stderr: $ EXECUTOR_DEV=1 EXECUTOR_DATA_DIR=${EXECUTOR_DATA_DIR:-apps/local/.executor-dev} bun run apps/cli/src/main.ts mcp --scope /home/runner/_work/executor/executor/apps/local
error: Cannot find module '@executor-js/execution' from '/home/runner/_work/executor/executor/packages/core/api/src/server/execution-stack.ts'
Bun v1.3.11 (Linux x64)
error: script "dev:cli" exited with code 1: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Array.<anonymous> local/cli-mcp-daemon-attach-stress.test.ts:258:86
❯ 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
|
|
[local] local/cli-mcp-daemon-attach-stress.test.ts > Local CLI MCP · an attach storm of concurrent stdio bridges all execute correctly:
e2e/local/cli-mcp-daemon-attach-stress.test.ts#L75
Error: daemon stdout closed before ready: $ EXECUTOR_DEV=1 EXECUTOR_DATA_DIR=${EXECUTOR_DATA_DIR:-apps/local/.executor-dev} bun run apps/cli/src/main.ts daemon run --foreground --port "0" --hostname "127.0.0.1" --scope /home/runner/_work/executor/executor/apps/local
error: Cannot find module '@executor-js/host-mcp' from '/home/runner/_work/executor/executor/packages/core/api/src/server/mcp-build.ts'
Bun v1.3.11 (Linux x64)
error: script "dev:cli" exited with code 1
❯ Socket.<anonymous> local/cli-mcp-daemon-attach-stress.test.ts:75:19
|
|
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/
|
|
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 (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, 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)
|
|
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, actions/upload-artifact@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.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 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 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 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 (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, 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 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 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 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 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, 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 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 (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, 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 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/
|
|
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 (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/
|
|
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, 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 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, 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 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, 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 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, 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 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 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 (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, actions/upload-artifact@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/
|
|
Self-host Docker image
Skipping sticky disk commit due to previous step failures
|
|
Self-host Docker image
- Step: unknown (failed)
|
|
Self-host Docker image
Found 2 failed/cancelled steps in previous workflow steps
|
|
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)
|
|
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.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 (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, 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 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, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|