feat: HyperAgent v0.1.0 — AI agent with sandboxed JS execution #9
simongdaviespr-validate.yml
on: push
Matrix: build-and-test
CI Status
3s
Annotations
21 errors and 8 warnings
|
tests/fs-read.test.ts > createHostFunctions > readFile > should reject non-string path:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should reject symlinks:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should reject dotfiles:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should reject path traversal:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should return error for non-existent file:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should fall back to utf8 for invalid encoding:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should return base64 when encoding is 'base64':
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should default to utf8 when encoding omitted:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should read file content as JSON envelope:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > should return exactly 6 read-only host functions:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should reject non-string path:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should reject symlinks:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should reject dotfiles:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should reject path traversal:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should return error for non-existent file:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should fall back to utf8 for invalid encoding:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should return base64 when encoding is 'base64':
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should default to utf8 when encoding omitted:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > readFile > should read file content as JSON envelope:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
tests/fs-read.test.ts > createHostFunctions > should return exactly 6 read-only host functions:
plugins/fs-read/index.js#L130
Error: [fs-read] O_NOFOLLOW not supported on this platform — cannot guarantee symlink safety
❯ createHostFunctions plugins/fs-read/index.js:130:15
❯ tests/fs-read.test.ts:262:23
|
|
CI Status
Process completed with exit code 1.
|
|
Lint & Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build & Test (mshv-release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build & Test (whp-debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build Docker Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build & Test (kvm-debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build & Test (kvm-release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build & Test (mshv-debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build & Test (whp-release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
hyperagent-linux-x64-kvm
Expired
|
88.8 MB |
sha256:63400994d4b60a218c94294bbb8b591d8e3c23ae882aaf93a0ca3ccac60f4e97
|
|
|
hyperagent-linux-x64-mshv
Expired
|
88.8 MB |
sha256:c3326012d523d446500501dc41cb89c425bc8ceefe26a63e39aa91e31998c631
|
|
|
hyperlight-dev~hyperagent~RL8C62.dockerbuild
|
70.8 KB |
sha256:98a552c7689e9d54e7bd4fc224feff4818ad51068e255186f7a27e831c642f53
|
|