Repository navigation
Allow longer provider stream pauses across chat models - #1167
Merged
Merged
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 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.
Long provider pauses can abort a streaming chat after two minutes even when generation may still be running, for example while an upstream buffers a complete tool-call argument. Raise OpenSecret's per-chunk idle timeout from 120 to 300 seconds for every chat model and provider, including the shared Responses provider executor.
Raise the shared proxy's SSE idle default from 300 to 360 seconds so the backend can return its structured timeout error before the relay closes the connection. Update CLI/library and Docker defaults, examples and documentation; prepare proxy 0.4.4 and align the embedded consumers' lock entries. Request-setup/non-streaming limits, cancellation, and retry policy are unchanged.
The tradeoff is a longer wait for a genuinely silent provider. This is a mitigation, not a claim that the suspected upstream tool-parser buffering bug is fixed. Existing proxy installations need an upgrade or an explicit idle-timeout override to get the extra margin.
Validation:
just cipassed: all four Clippy feature configurations, warning-denied workspace build/tests, and ACP/proxy headless tests.No deployment, registry publication, or production configuration change is included. Recovery of a live Tinfoil tool call within the new five-minute limit remains unverified.
Hosted CI currently reports pre-existing Research
zipadvisories RUSTSEC-2026-0367, RUSTSEC-2026-0368 and RUSTSEC-2026-0369. The affectedzipversions (4.6.1 and 8.6.0) are unchanged from base commit 883ac72. See the supply-chain check. Dependency remediation is outside this timeout change.