feat: Add global request_timeout configuration #834
+5
−0
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
Adds a global
request_timeoutconfiguration toconfig/prism.php.Why
When I run models that require long generation times (e.g., Gemini 3 Pro with more than 50,000 input tokens) often exceed the default 30-second timeout. Previously, I had to manually configure the client for each instance, which was so troublesome. Furthermore, there was no official documentation for the timeout in the PrismPHP document.
This change allows setting a global timeout via the
PRISM_REQUEST_TIMEOUTenvironment variable.Changes
request_timeouttoconfig/prism.php(default: 30s as before).InitializesClientto apply this timeout to the base HTTP client.