fix: enforce native stream deadlines - #22
Merged
haolpku merged 1 commit intoSep 20, 2026
Merged
Conversation
DevChiniwala
force-pushed
the
codex/enforce-native-stream-deadlines
branch
from
September 17, 2026 10:51
c19b432 to
bf3cc94
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NativeAgentLoop.run_turn applied wall_clock_timeout_s around model calls, but stream_turn awaited the provider stream without a deadline. A stalled provider could therefore keep /api/chat open indefinitely. Added the same configured deadline around each native model stream and emit the existing structured error event on timeout, including cancellation of the provider iterator. Regression uses a hanging protocol-neutral client and verifies bounded completion plus cleanup. Validation: 10 native agent-loop tests passed and compileall passed; no API shape change; targets main.