Repository navigation
fix(gateway): increase Envoy buffer and extproc timeout for semantic router - #23
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
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.
What
Increase the Envoy Gateway client buffer from its 32 KiB default to 4 MiB. Update the Semantic Router Envoy external-processing timeout from 10 seconds to the documented 60 seconds while retaining buffered request/response processing.
Why
Coding-agent requests include large system prompts and tool schemas that can exceed Envoy Gateway’s default 32 KiB buffer, causing HTTP 413 responses before requests reach Semantic Router or vLLM. The longer ext-proc timeout follows Semantic Router’s documented Envoy integration and provides sufficient time for request classification and processing.
Checklist
mise run cipasses