Add 5-minute timeout control for model warming in /initialize route #12
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.
Problem
The
/initializeroute insrc/code/agent/routes/routes.pycould hang indefinitely during the model warming phase (calls toServerlessApiService().run()andapi_clear_history()), causing initialization timeouts and potential cost issues in serverless environments.Solution
Added timeout control using
ThreadPoolExecutorwith a 5-minute (300 seconds) maximum wait time for the model warming section.Changes Made
ThreadPoolExecutorwith 300-second timeoutCode Changes
Behavior
Testing
This ensures the initialization process never hangs indefinitely while maintaining backward compatibility and preserving all existing error handling logic.
This pull request was created as a result of the following prompt from Copilot chat.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.