4fc0975d22
The retrieve_batch endpoint sets batch status to "complete" but never set batch_processed=True, permanently blocking file deletion. CheckBatchCost (the safety net) also excluded completed batches from its primary query, so batch_processed was never set by either path. Three fixes: 1. update_batch_in_database sets batch_processed=True when status reaches "complete", with old-schema fallback retry 2. CheckBatchCost primary query no longer excludes complete/completed (batch_processed=False filter prevents reprocessing) 3. retrieve_batch early-return now includes "complete" (DB-normalized spelling) to avoid unnecessary provider re-polls Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| bedrock_batch_completions.jsonl | ||
| input_azure.jsonl | ||
| input.jsonl | ||
| openai_batch_completions.jsonl | ||
| openai_fine_tuning.jsonl | ||
| out_azure.jsonl | ||
| out.jsonl | ||
| test_batch_rate_limiting_integration.jsonl | ||
| test_bedrock_batches_api.py | ||
| test_e2e_openai_responses_api.py | ||
| test_openai_batches_endpoint.py | ||
| test_openai_files_endpoints.py | ||
| test_openai_fine_tuning.py | ||
| test_responses_websocket_proxy_e2e.py | ||