server: expose uvicorn timeout_keep_alive in config#667
Merged
Pangjiping merged 1 commit intoalibaba:mainfrom Apr 8, 2026
Merged
server: expose uvicorn timeout_keep_alive in config#667Pangjiping merged 1 commit intoalibaba:mainfrom
Pangjiping merged 1 commit intoalibaba:mainfrom
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.
Summary
server.timeout_keep_aliveto the server config and default it to30app_config.server.timeout_keep_aliveinto bothuvicorn.run(...)entrypoints5s)Motivation:
JavaScript/Python/Kotlin SDKs all keep idle pooled HTTP connections around for about 30 seconds. The lifecycle server was still using uvicorn's default
timeout_keep_alive=5, which makes stale keep-alive reuse more likely and can surface as transientECONNRESETon follow-up requests.Testing
Not run because this change only wires an existing uvicorn runtime option through server config. Validation should be done by restarting the server and verifying requests after short idle gaps no longer hit the previous default behavior.
Breaking Changes
Checklist
Backward compatibility:
server.timeout_keep_aliveis omitted, the server now defaults to30instead of inheriting uvicorn's implicit5