docs(ai-proxy): restore max_stream_duration_ms and max_response_bytes#13539
Open
AlinsRan wants to merge 1 commit into
Open
docs(ai-proxy): restore max_stream_duration_ms and max_response_bytes#13539AlinsRan wants to merge 1 commit into
AlinsRan wants to merge 1 commit into
Conversation
These two streaming/response safeguard fields are defined in the plugin schema but were dropped from the attribute table, leaving the guardrails undocumented. Restore both rows (en + zh) and the per-socket clarification on the `timeout` description. Signed-off-by: AlinsRan <alinsran@apache.org>
dosubot
Bot
added
size:XS
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 this fixes
The
max_stream_duration_msandmax_response_bytessafeguards are implemented and present in the ai-proxy plugin schema, but they are undocumented — the attribute table indocs/{en,zh}/latest/plugins/ai-proxy.mddoes not list them.Source
timeoutdescription — likely an unintended drop from a stale branch. The schema fields remain (apisix/plugins/ai-proxy/schema.lualines 254 / 263 and 379 / 388), so the guardrails exist but are invisible to users.Change (docs only)
max_stream_duration_msandmax_response_bytesrows in bothdocs/enanddocs/zh.timeoutdescription ("Applied per socket operation … does not cap the total duration of a streaming response").Checklist