Codex Update #70
ishulginAnnotations
10 errors and 2 warnings
|
update:
src/__tests__/CodexACPAgent/mcp-session.test.ts#L22
Property 'CODEX_HOME' comes from an index signature, so it must be accessed with ['CODEX_HOME'].
|
|
update:
src/__tests__/CodexACPAgent/mcp-session.test.ts#L21
Property 'HOME' comes from an index signature, so it must be accessed with ['HOME'].
|
|
update:
src/__tests__/CodexACPAgent/mcp-session.test.ts#L19
Property 'CODEX_HOME' comes from an index signature, so it must be accessed with ['CODEX_HOME'].
|
|
update:
src/__tests__/CodexACPAgent/mcp-session.test.ts#L18
Property 'HOME' comes from an index signature, so it must be accessed with ['HOME'].
|
|
src/__tests__/CodexACPAgent/mcp-session.test.ts > MCP session configuration > should return configured mcp:
src/__tests__/CodexACPAgent/mcp-session.test.ts#L39
Error: ENOTEMPTY: directory not empty, rmdir '/tmp/codex-acp-mcp-home-5JSF4y/.codex'
❯ src/__tests__/CodexACPAgent/mcp-session.test.ts:39:12
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -39, code: 'ENOTEMPTY', syscall: 'rmdir', path: '/tmp/codex-acp-mcp-home-5JSF4y/.codex' }
|
|
src/__tests__/CodexACPAgent/mcp-session.test.ts > MCP session configuration > should return configured mcp:
src/CodexAcpServer.ts#L817
RequestError: Codex process has exited with code 1
❯ CodexAcpServer.runWithProcessCheck src/CodexAcpServer.ts:817:23
❯ CodexAcpServer.initialize src/CodexAcpServer.ts:92:9
❯ src/__tests__/CodexACPAgent/mcp-session.test.ts:44:9
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 1001, data: undefined, toResult: 'Function<toResult>', toErrorResponse: 'Function<toErrorResponse>' }
|
|
src/__tests__/CodexACPAgent/mcp-session.test.ts > MCP session configuration > should return configured mcp:
src/CodexAcpServer.ts#L817
RequestError: Codex process has exited with code 1
❯ CodexAcpServer.runWithProcessCheck src/CodexAcpServer.ts:817:23
❯ CodexAcpServer.initialize src/CodexAcpServer.ts:92:9
❯ src/__tests__/CodexACPAgent/mcp-session.test.ts:44:9
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 1001, data: undefined, toResult: 'Function<toResult>', toErrorResponse: 'Function<toErrorResponse>' }
|
|
src/__tests__/CodexACPAgent/mcp-session.test.ts > MCP session configuration > should return configured mcp:
src/CodexAcpServer.ts#L817
RequestError: Codex process has exited with code 1
❯ CodexAcpServer.runWithProcessCheck src/CodexAcpServer.ts:817:23
❯ CodexAcpServer.initialize src/CodexAcpServer.ts:92:9
❯ src/__tests__/CodexACPAgent/mcp-session.test.ts:44:9
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 1001, data: undefined, toResult: 'Function<toResult>', toErrorResponse: 'Function<toErrorResponse>' }
|
|
update:
src/CodexEventHandler.ts#L133
Type '"thread/realtime/transcriptUpdated"' is not comparable to type '"error" | "thread/started" | "thread/status/changed" | "thread/archived" | "thread/unarchived" | "thread/closed" | "skills/changed" | "thread/name/updated" | "thread/tokenUsage/updated" | ... 44 more ... | "account/login/completed"'.
|
|
update:
src/CodexEventHandler.ts#L64
Function lacks ending return statement and return type does not include 'undefined'.
|
|
check
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 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/
|
|
update
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/create-github-app-token@v1, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
|