Public hardening followups (Codex CLI docs, Slice 3, capability evidence, auto-block, vault v3 design) #11
ARHAEEMAnnotations
17 errors and 4 warnings
|
build-and-test (ubuntu-latest, 22)
Process completed with exit code 1.
|
|
packages/mcp-server/test/daemon/cloudflared-named-provider.test.js > stop() > SIGTERM first; if the process doesn't exit within the grace window, escalate to SIGKILL (POSIX):
packages/mcp-server/test/daemon/cloudflared-named-provider.test.js#L447
AssertionError: expected [ 'SIGTERM' ] to include 'SIGKILL'
❯ packages/mcp-server/test/daemon/cloudflared-named-provider.test.js:447:29
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > case-insensitive blacklist matching > matches CODE.EXE the same as code.exe on Windows:
packages/extension/tests/validate-command.test.ts#L241
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality
Expected: "wrong-runtime"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:241:9
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\Windsurf - Next\Windsurf - Next.exe as wrong-runtime:
packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality
Expected: "wrong-runtime"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:159:42
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\cursor\Cursor.exe as wrong-runtime:
packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality
Expected: "wrong-runtime"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:159:42
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\Microsoft VS Code\Code.exe as wrong-runtime:
packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality
Expected: "wrong-runtime"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:159:42
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: missing on disk > returns missing for stale Windows path:
packages/extension/tests/validate-command.test.ts#L141
AssertionError: expected 'unknown' to be 'missing' // Object.is equality
Expected: "missing"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:141:9
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: node-shaped + exists > returns ok for Windows node.exe path that exists:
packages/extension/tests/validate-command.test.ts#L127
AssertionError: expected 'unknown' to be 'ok' // Object.is equality
Expected: "ok"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:127:9
|
|
build-and-test (ubuntu-latest, 20)
Process completed with exit code 1.
|
|
packages/mcp-server/test/daemon/cloudflared-named-provider.test.js > stop() > SIGTERM first; if the process doesn't exit within the grace window, escalate to SIGKILL (POSIX):
packages/mcp-server/test/daemon/cloudflared-named-provider.test.js#L447
AssertionError: expected [ 'SIGTERM' ] to include 'SIGKILL'
❯ packages/mcp-server/test/daemon/cloudflared-named-provider.test.js:447:29
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > case-insensitive blacklist matching > matches CODE.EXE the same as code.exe on Windows:
packages/extension/tests/validate-command.test.ts#L241
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality
Expected: "wrong-runtime"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:241:9
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\Windsurf - Next\Windsurf - Next.exe as wrong-runtime:
packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality
Expected: "wrong-runtime"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:159:42
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\cursor\Cursor.exe as wrong-runtime:
packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality
Expected: "wrong-runtime"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:159:42
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: blacklisted runtime basename > flags C:\Users\me\AppData\Local\Programs\Microsoft VS Code\Code.exe as wrong-runtime:
packages/extension/tests/validate-command.test.ts#L159
AssertionError: expected 'unknown' to be 'wrong-runtime' // Object.is equality
Expected: "wrong-runtime"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:159:42
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: missing on disk > returns missing for stale Windows path:
packages/extension/tests/validate-command.test.ts#L141
AssertionError: expected 'unknown' to be 'missing' // Object.is equality
Expected: "missing"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:141:9
|
|
packages/extension/tests/validate-command.test.ts > validateCommand > absolute path: node-shaped + exists > returns ok for Windows node.exe path that exists:
packages/extension/tests/validate-command.test.ts#L127
AssertionError: expected 'unknown' to be 'ok' // Object.is equality
Expected: "ok"
Received: "unknown"
❯ packages/extension/tests/validate-command.test.ts:127:9
|
|
build-and-test (windows-latest, 22)
Process completed with exit code 1.
|
|
build-and-test (ubuntu-latest, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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-and-test (ubuntu-latest, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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-and-test (windows-latest, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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-and-test (windows-latest, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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/
|