fix(batches): drop the env-var override for the input-file read timeout

BATCH_INPUT_FILE_READ_TIMEOUT_SECONDS failed the documentation gate, which
requires every env var to be documented in the environment-settings reference
(that lives in the litellm-docs repo, not here).

The env var was redundant anyway: general_settings.batch_input_file_read_timeout
already makes the deadline configurable per deployment, which is what was asked
for. Keeping only the general_settings key leaves one documented way to set it.
This commit is contained in:
mubashir1osmani 2026-07-31 16:39:06 -07:00
parent f1c4a40fab
commit 80f2932146

View file

@ -1379,9 +1379,9 @@ BATCH_STATUS_POLL_MAX_ATTEMPTS = int(os.getenv("BATCH_STATUS_POLL_MAX_ATTEMPTS",
# Deadline for the batch rate limiter's input-file read. The read happens inline
# in POST /v1/batches, so it must resolve well within a client's read timeout;
# unbounded, the OpenAI SDK default (600s, max_retries=2) applies and a stalled
# Files API holds the request open indefinitely. Override per-deployment with
# Files API holds the request open indefinitely. Override with
# general_settings.batch_input_file_read_timeout.
DEFAULT_BATCH_INPUT_FILE_READ_TIMEOUT_SECONDS = float(os.getenv("BATCH_INPUT_FILE_READ_TIMEOUT_SECONDS", 10))
DEFAULT_BATCH_INPUT_FILE_READ_TIMEOUT_SECONDS = 10.0
HEALTH_CHECK_TIMEOUT_SECONDS = int(os.getenv("HEALTH_CHECK_TIMEOUT_SECONDS", 60)) # 60 seconds
_background_health_check_max_tokens_env = os.getenv("BACKGROUND_HEALTH_CHECK_MAX_TOKENS")