Skip to content

Feat timeout#11

Merged
overcuriousity merged 3 commits intonew-featuresfrom
feat--timeout
Jan 31, 2026
Merged

Feat timeout#11
overcuriousity merged 3 commits intonew-featuresfrom
feat--timeout

Conversation

@overcuriousity
Copy link
Owner

No description provided.

overcuriousity and others added 3 commits January 30, 2026 15:22
The requestTimeout feature was not working because the timeout
context was not connected to the HTTP request. When the timeout
fired, it attempted to kill the process but the reverse proxy
continued waiting for a response indefinitely.

- Use context.WithTimeout() to create a timeout context for the HTTP request
- Clone the request with the timeout context before proxying
- When timeout fires, the HTTP request is immediately cancelled
- Fix StopImmediately() to handle timeouts during model loading (StateStarting)
- Add unit test to verify timeout behavior

Before: requests would run for 60+ seconds despite requestTimeout: 20
After: requests terminate in exactly 20 seconds as configured

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Add brief mention of requestTimeout feature in the customizable
features section of README.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@overcuriousity overcuriousity merged commit fc33fdf into new-features Jan 31, 2026
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.

1 participant