bump default request timeout 30s -> 60s#9
Closed
goharanwar wants to merge 1 commit into
Closed
Conversation
Agent execution involves LLM generation that routinely takes >30s in staging; the prior default caused test_execute_agent_query to fail with 408 client timeouts while the server completed the request successfully in ~57s. The new default matches the existing budget asserted by test_execute_agent_response_time (< 60_000ms). Other endpoints' SLA assertions all remain well under 60s (auth < 5s, get/list corpus < 5s, indexing < 10s, rag summary < 30s, query < 5s), so the bump only buys headroom for agent calls. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Closing — fixing in vectara/platform PR #5450 instead since the test suite is being moved into the platform monorepo. |
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
1 participant
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
VECTARA_TIMEOUTdefault from 30s to 60s inutils/config.pyWhy
Smoke tests on admin-ops staging were failing
test_execute_agent_querywith408 - Request timeoutafter exactly 30,020ms. Agents-api logs (request_id=db4cb451336142a6b0a38b3607cc5c45, 2026-05-20 15:18:15 → 15:19:12) show the server completed the LLM call successfully — 57s end-to-end. The test client gave up at the 30s default before the server replied.The suite already declares 60s as the acceptable budget for agent execution in
test_execute_agent_response_time(assert response.elapsed_ms < 60000). The 30s default contradicted that. This change makes the default consistent with the suite's own SLA.Sanity check on other tests
All response-time assertions in the suite remain well under 60s, so the bump is purely additive headroom for agent calls:
test_authentication_response_timetest_get_corpus_response_timetest_list_corpora_response_timetest_metadata(indexing)test_rag_summarytest_query_edge_casestest_execute_agent_response_timeTest plan
agentsprofile;test_execute_agent_queryshould pass