Skip to content

Fixes an issue where eval-system may return empty or incomplete output for valid commands #3039

Open
afrdbaig7 wants to merge 1 commit intoMoganLab:mainfrom
afrdbaig7:afrdbaig7/200_27/fix_eval_system_timeout
Open

Fixes an issue where eval-system may return empty or incomplete output for valid commands #3039
afrdbaig7 wants to merge 1 commit intoMoganLab:mainfrom
afrdbaig7:afrdbaig7/200_27/fix_eval_system_timeout

Conversation

@afrdbaig7
Copy link

Fixes #2221
What changed
Increased the default timeout from 20 ms to 5000 ms

Why
The previous timeout (~500 ms total with retries) is too aggressive for real-world commands (e.g., Python or shell scripts), causing the read loop to exit before output is fully available.
A 5-second timeout is a safer default while still avoiding the risk of hanging indefinitely.

Scope
This change is limited to adjusting the timeout value. No other subprocess behavior is modified.

Tests
Added tests to cover:
slow commands (e.g., time.sleep(1))
commands with no output
normal fast commands

… output

Bumped default pipe timeout from 20ms to 5000ms. Stops slow commands (like python snippets) from silently cutting off early. Changed pipe polling to append to result string instead of silently cutting large outputs at an 8KB buffer limit. Added test coverage for slow, empty, and large output cases.
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.

Timeout on eval-system too agressive?

1 participant