Repository navigation
Merge pull request #2 from JngyEn/feat/feishu-run-card-refresh-and-ap… #148
baibairuiAnnotations
8 errors and 1 warning
|
test
Process completed with exit code 1.
|
|
tests/deploy-script.test.ts > deploy.sh > refreshes remote dependencies when lockfile changes instead of failing the deploy:
tests/deploy-script.test.ts#L8
Error: ENOENT: no such file or directory, open '/home/runner/work/codex-gateway/codex-gateway/deploy.sh'
❯ readScript tests/deploy-script.test.ts:8:13
❯ tests/deploy-script.test.ts:13:20
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -2, code: 'ENOENT', syscall: 'open', path: '/home/runner/work/codex-gateway/codex-gateway/deploy.sh' }
|
|
tests/codex-runner.test.ts > CodexRunner > does not kill an active run when stdout activity keeps arriving before the idle timeout:
tests/codex-runner.test.ts#L1050
AssertionError: promise rejected "Error: codex app-server exited with code 0" instead of resolving
❯ tests/codex-runner.test.ts:1050:28
Caused by: Caused by: Error: codex app-server exited with code 0
❯ EventEmitter.<anonymous> src/services/codex-app-server-client.ts:114:20
❯ tests/codex-runner.test.ts:1048:11
|
|
tests/codex-runner.test.ts > CodexRunner > fails before spawn when the configured codex binary is unavailable:
src/services/codex-app-server-client.ts#L87
TypeError: Cannot read properties of undefined (reading 'stdout')
❯ new CodexAppServerClient src/services/codex-app-server-client.ts:87:16
❯ CodexRunner.runWithAppServer src/services/codex-runner.ts:597:20
❯ CodexRunner.runWithControl src/services/codex-runner.ts:198:19
❯ CodexRunner.run src/services/codex-runner.ts:193:17
❯ tests/codex-runner.test.ts:1013:25
|
|
tests/chat-handler.test.ts > createChatHandler > streams feishu snapshots through the dedicated sender and skips a duplicate final flush:
tests/chat-handler.test.ts#L2940
AssertionError: expected '默认助手 ·\n第二段' to be '默认助手 ·\n第一段默认助手 ·\n第二段' // Object.is equality
- Expected
+ Received
默认助手 ·
- 第一段默认助手 ·
第二段
❯ tests/chat-handler.test.ts:2940:50
|
|
tests/chat-handler.test.ts > createChatHandler > keeps running when the progress status push fails:
tests/chat-handler.test.ts#L1463
AssertionError: expected 1st "vi.fn()" call to have been called with [ 'wecom', 'u1', …(1) ]
- Expected
+ Received
[
"wecom",
"u1",
"默认助手 ·
- ⏳ 已接收请求，正在处理...",
+ 第一条回复",
]
❯ tests/chat-handler.test.ts:1463:22
|
|
tests/chat-handler.test.ts > createChatHandler > pushes help text automatically when a new wecom session starts:
tests/chat-handler.test.ts#L1424
AssertionError: expected 3rd "vi.fn()" call to have been called with [ 'wecom', 'u1', …(1) ]
- Expected
+ Received
[
"wecom",
"u1",
"默认助手 ·
- ⏳ 已接收请求，正在处理...",
+ 开始处理。",
]
❯ tests/chat-handler.test.ts:1424:22
|
|
tests/chat-handler.test.ts > createChatHandler > renders current agent and shared memory summary via /memory:
tests/chat-handler.test.ts#L1081
AssertionError: expected "vi.fn()" to be called with arguments: [ 'wecom', 'u1', StringContaining{…} ]
Received:
1st vi.fn() call:
[
"wecom",
"u1",
- StringContaining "【Shared Memory】",
+ "当前 agent：默认Agent (default)
+ 工作区：/repo/default
+
+ 【User Identity】
+ 1. identity.md: 叫我白瑞 / 中文交流 / 不弄虚作假
+
+ 【Agent Identity】
+ 1. projects.md: wecom-codex-gateway 优化中",
]
Number of calls: 1
❯ tests/chat-handler.test.ts:1081:22
|
|
test
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. 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/
|