Tianyi Cui
8a79679489
The bridge replaces its serialization queue with a pool that reuses the native concurrency contract: submissions classify through registry.executionMode (fail-closed isConcurrencySafe), start strictly in submission order, overlap up to the validated maxParallelSubCalls config (default 10; 1 restores serial), and exclusive calls drain the pool, run alone, and bar later calls. Each started sub-call logs a tool/code-dispatch-start event at pool entry; the existing tool/code-dispatch settles the pair (started ⇔ settles exactly once; abandoned queued calls log neither). SDK prompt guidance now states the true Promise.all contract — re-recorded across every code/both-mode snapshot (plus the stale cordis-dynamic-toolchain fixture gaining the required description arg). Client: CodeSubCall widens to RunningToolCall | ToolResultNode — starts land the running shape (rows wear the native running ring), settles replace in place preserving start order, callTime pairs to the start time. Fixture emits start/settle pairs; jsdom pins the running sub-row; runtime specs pin in-place settlement and out-of-order completion.
138 lines
8.0 KiB
Plaintext
138 lines
8.0 KiB
Plaintext
terminal 100x36 buffer=normal length=66 base=30 viewport=30
|
|
lifecycle started=1 stopped=0 progress=inactive
|
|
title "Using ONE run_code program: call — DSH TUI snapshot"
|
|
cursor hidden column=1 viewportRow=31 bufferRow=61
|
|
buffer
|
|
0| " DEEPSEEK HARNESS"
|
|
style 1-8 fg=bright-blue bold
|
|
style 10-16 bold
|
|
1| " Using ONE run_code program: call"
|
|
style 1-32 fg=bright-black
|
|
2| " deepseek-v4-flash • main-session"
|
|
style 1-34 dim
|
|
3| <blank>
|
|
4| "▌ "
|
|
style 0-0 fg=bright-blue
|
|
5| "▌ You "
|
|
style 0-0 fg=bright-blue
|
|
style 2-4 fg=bright-blue bold
|
|
6| "▌ Using ONE run_code program: call the bash tool twice — exactly echo CODE_ONE then exactly echo "
|
|
style 0-0 fg=bright-blue
|
|
style 65-77 fg=cyan
|
|
style 92-99 fg=cyan
|
|
7| "▌ CODE_TWO. Inside that same program, console.log exactly captured output, then return the two "
|
|
style 0-0 fg=bright-blue
|
|
style 2-9 fg=cyan
|
|
style 58-72 fg=cyan
|
|
8| "▌ outputs joined with a plus sign. Reply with that joined string only and stop. "
|
|
style 0-0 fg=bright-blue
|
|
9| "▌ "
|
|
style 0-0 fg=bright-blue
|
|
10| <blank>
|
|
11| " Reasoning "
|
|
style 1-9 fg=bright-black italic
|
|
12| " The user wants me to write a single run_code program that: "
|
|
style 1-36 fg=bright-black italic
|
|
style 37-44 fg=cyan
|
|
style 45-58 fg=bright-black italic
|
|
13| " 1. Calls bash tool twice - first with echo CODE_ONE, then with echo CODE_TWO "
|
|
style 1-3 fg=bright-blue
|
|
style 4-9 fg=bright-black italic
|
|
style 10-13 fg=cyan
|
|
style 14-38 fg=bright-black italic
|
|
style 39-51 fg=cyan
|
|
style 52-63 fg=bright-black italic
|
|
style 64-76 fg=cyan
|
|
14| " 2. console.log exactly captured output "
|
|
style 1-3 fg=bright-blue
|
|
style 4-14 fg=cyan
|
|
style 15-23 fg=bright-black italic
|
|
style 24-38 fg=cyan
|
|
15| " 3. Returns the two outputs joined with a plus sign "
|
|
style 1-3 fg=bright-blue
|
|
style 4-50 fg=bright-black italic
|
|
16| " "
|
|
17| " Let me think about the structure. The bash tool returns an object with stdout/stderr. I need to "
|
|
style 1-38 fg=bright-black italic
|
|
style 39-42 fg=cyan
|
|
style 43-99 fg=bright-black italic
|
|
18| " extract the stdout text from each call. "
|
|
style 1-39 fg=bright-black italic
|
|
19| " "
|
|
20| " Looking at the bash output type: "
|
|
style 1-32 fg=bright-black italic
|
|
21| " "
|
|
22| " ``` "
|
|
style 1-3 dim
|
|
23| " { "
|
|
24| " kind: \"foreground\"; "
|
|
25| " exitCode: number | null; "
|
|
26| " signal: string | null; "
|
|
27| " timedOut: boolean; "
|
|
28| " aborted: boolean; "
|
|
29| " timeoutMs: number; "
|
|
30| " stdout: { "
|
|
31| " text: string; "
|
|
32| " truncated: boolean; "
|
|
33| " spillPath?: string; "
|
|
34| " }; "
|
|
35| " stderr: { ... }; "
|
|
36| " sandbox?: { ... }; "
|
|
37| " } "
|
|
38| " ``` "
|
|
style 1-3 dim
|
|
39| " "
|
|
40| " So I need to access .stdout.text from each result. "
|
|
style 1-20 fg=bright-black italic
|
|
style 21-32 fg=cyan
|
|
style 33-50 fg=bright-black italic
|
|
41| " "
|
|
42| " Let me write the program. "
|
|
style 1-25 fg=bright-black italic
|
|
43| <blank>
|
|
44| "▌ "
|
|
style 0-0 fg=green
|
|
45| "▌ ✓ Call bash twice, log, join outputs "
|
|
style 0-0 fg=green
|
|
style 2-2 fg=green bold
|
|
style 3-37 bold
|
|
46| "▌ captured output "
|
|
style 0-0 fg=green
|
|
47| "▌ CODE_ONE+CODE_TWO "
|
|
style 0-0 fg=green
|
|
48| "▌ "
|
|
style 0-0 fg=green
|
|
49| <blank>
|
|
50| " Reasoning "
|
|
style 1-9 fg=bright-black italic
|
|
51| " The program ran successfully. The output shows: "
|
|
style 1-47 fg=bright-black italic
|
|
52| " - captured output (from console.log) "
|
|
style 1-2 fg=bright-blue
|
|
style 3-17 fg=cyan
|
|
style 18-36 fg=bright-black italic
|
|
53| " - CODE_ONE+CODE_TWO (the returned joined string) "
|
|
style 1-2 fg=bright-blue
|
|
style 3-19 fg=cyan
|
|
style 20-48 fg=bright-black italic
|
|
54| " "
|
|
55| " The user asked me to reply with that joined string only and stop. So I'll reply with just "
|
|
style 1-99 fg=bright-black italic
|
|
56| " CODE_ONE+CODE_TWO. "
|
|
style 1-17 fg=cyan
|
|
style 18-18 fg=bright-black italic
|
|
57| <blank>
|
|
58| " Assistant "
|
|
style 1-9 fg=bright-magenta bold
|
|
59| " CODE_ONE+CODE_TWO "
|
|
60| "────────────────────────────────────────────────────────────────────────────────────────────────────"
|
|
style 0-99 dim
|
|
61| " "
|
|
style 1-1 inverse
|
|
62| "────────────────────────────────────────────────────────────────────────────────────────────────────"
|
|
style 0-99 dim
|
|
63| "deepseek-v4-flash /workspace/project ↑182 ↓446 cache 98% 4% context tools:c"
|
|
style 0-78 dim
|
|
style 81-99 dim
|
|
64-65| <blank>
|