docs: correct visible-output watchdog to share request timeout budget - #144
Merged
WilliamAGH merged 1 commit intoJul 29, 2026
Conversation
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The streaming configuration entry in docs/configuration.md claimed Java Chat enforces a separate 20-second visible-output deadline. After the watchdog was changed to share streamingRequestTimeout(), that description is stale: the visible-output deadline now uses the same configured OPENAI_STREAMING_REQUEST_TIMEOUT_SECONDS budget rather than a hardcoded 20s.
Example: a developer debugging a slow first-token stream (e.g. non-none reasoning effort) would expect the watchdog to cut off output at 20s even when the request budget is higher, leading them to chase the wrong timeout.
Introduced by commit af4d7d2 (@WilliamAGH)
Doc Drift PRs can be configured here.