Skip to content

Handle tool and permission broadcasts via event model (protocol v3) #571

Handle tool and permission broadcasts via event model (protocol v3)

Handle tool and permission broadcasts via event model (protocol v3) #571

Triggered via pull request March 7, 2026 13:30
Status Failure
Total duration 4m 26s
Artifacts

nodejs-sdk-tests.yml

on: pull_request
Matrix: Node.js SDK Tests
Fit to window
Zoom out
Zoom in

Annotations

8 errors
Node.js SDK Tests (windows-latest)
Process completed with exit code 1.
test/e2e/session.test.ts > Send Blocking Behavior > send returns immediately while events stream in background: nodejs/test/e2e/session.test.ts#L350
Error: Test timed out in 30000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/e2e/session.test.ts:350:5
Node.js SDK Tests (windows-latest): nodejs/test/e2e/session.test.ts#L0
No cached response found for POST /chat/completions. Final message: {"role":"tool","tool_call_id":"toolcall_1","content":"<command with shellId: 0 is still running after 30 seconds. The command is still running but hasn't produced output yet. It may be waiting for input or still processing. Use read_powershell to continue waiting, write_powershell if you think it needs input, or stop_powershell to stop it.>"}
Node.js SDK Tests (windows-latest): nodejs/test/e2e/session.test.ts#L0
No cached response found for POST /chat/completions. Final message: {"role":"tool","tool_call_id":"toolcall_1","content":"<command with shellId: 0 is still running after 30 seconds. The command is still running but hasn't produced output yet. It may be waiting for input or still processing. Use read_powershell to continue waiting, write_powershell if you think it needs input, or stop_powershell to stop it.>"}
Node.js SDK Tests (windows-latest): nodejs/test/e2e/session.test.ts#L0
No cached response found for POST /chat/completions. Final message: {"role":"tool","tool_call_id":"toolcall_1","content":"<command with shellId: 0 is still running after 30 seconds. The command is still running but hasn't produced output yet. It may be waiting for input or still processing. Use read_powershell to continue waiting, write_powershell if you think it needs input, or stop_powershell to stop it.>"}
Node.js SDK Tests (windows-latest): nodejs/test/e2e/session.test.ts#L0
No cached response found for POST /chat/completions. Final message: {"role":"tool","tool_call_id":"toolcall_1","content":"<command with shellId: 0 is still running after 30 seconds. The command is still running but hasn't produced output yet. It may be waiting for input or still processing. Use read_powershell to continue waiting, write_powershell if you think it needs input, or stop_powershell to stop it.>"}
Node.js SDK Tests (windows-latest): nodejs/test/e2e/session.test.ts#L0
No cached response found for POST /chat/completions. Final message: {"role":"tool","tool_call_id":"toolcall_1","content":"<command with shellId: 0 is still running after 30 seconds. The command is still running but hasn't produced output yet. It may be waiting for input or still processing. Use read_powershell to continue waiting, write_powershell if you think it needs input, or stop_powershell to stop it.>"}
Node.js SDK Tests (windows-latest): nodejs/test/e2e/session.test.ts#L0
No cached response found for POST /chat/completions. Final message: {"role":"tool","tool_call_id":"toolcall_1","content":"<command with shellId: 0 is still running after 30 seconds. The command is still running but hasn't produced output yet. It may be waiting for input or still processing. Use read_powershell to continue waiting, write_powershell if you think it needs input, or stop_powershell to stop it.>"}