Skip to content

Apply DSTACK_SERVICE_CLIENT_TIMEOUT to gateway nginx and app - #4327

Merged
r4victor merged 3 commits into
masterfrom
issue_4239_gateway_read_timeout
Sep 30, 2026
Merged

r4victor merged 3 commits into
masterfrom
issue_4239_gateway_read_timeout

Conversation

@r4victor

Copy link
Copy Markdown
Collaborator

Fixes #4239

  • DSTACK_SERVICE_CLIENT_TIMEOUT is now passed to gateways on service registration and applied to nginx proxy_read_timeout (previously hardcoded to 300s) and to the gateway app's httpx client used by the model entrypoint (previously fixed at 60s).
  • The default is raised from 60 to 300 seconds to match the previous nginx timeout.

The change applies only to services registered after the update.

The server now passes the timeout to gateways on service and entrypoint
registration. The default is raised from 60 to 300 seconds to match the
previous nginx timeout.
@r4victor
r4victor merged commit 878efad into master Sep 30, 2026
26 checks passed
@r4victor
r4victor deleted the issue_4239_gateway_read_timeout branch September 30, 2026 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Gateway proxy_read_timeout is hardcoded to 300s, truncating slow long-context streaming responses

1 participant