Skip to content

fix(orchestrate): demux Docker logs in a loop, not by recursion - #16

Merged
psanders merged 1 commit into
mainfrom
fix/demux-iterative
Nov 5, 2026
Merged

psanders merged 1 commit into
mainfrom
fix/demux-iterative

Conversation

@psanders

@psanders psanders commented Nov 5, 2026

Copy link
Copy Markdown
Member

Routr's 6-hour soak (run 41898433488) failed at the end with the agent failed: Maximum call stack size exceeded. demuxLogs recursed once per Docker log frame. cat sampler-uut.jsonl over SSH for a 6.5-hour run produced enough small frames to overflow the stack. The 1-hour soak's file was small enough to get by.

The fix is a plain loop. The new test demuxes 200,000 one-line frames: it fails on main with RangeError: Maximum call stack size exceeded and passes now. 445 tests pass. Version 0.1.10.

Not in this PR: when the agent fails, the workflow's cleanup deletes the droplets before any raw results are downloaded, so the 6 hours of data were lost.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WSt25Wd7udAq3aj47MKn5J

demuxLogs recursed once per log frame. Reading a 6-hour soak's sampler
file from the UUT over SSH produced enough frames to overflow the call
stack, and the agent failed with "Maximum call stack size exceeded" at the
end of the run.
@psanders
psanders merged commit 03d58db into main Nov 5, 2026
@psanders
psanders deleted the fix/demux-iterative branch November 5, 2026 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant