yucheng-berri fc5ab31fba refactor(proxy/batches): make managed-file resolution purely additive, fall back like base (#34584) ... Restore the original PR's behavior on every path that did not already resolve: no database, a lookup error, a missing managed-file row, or a row without a storage_url all fall back to dispatching the original id, which the managed-files deployment hook still maps. This drops the 404 and 503 fail-closed responses I had added, which were the only behaviors that diverged from litellm_internal_staging. The change is now strictly additive: when a managed-file row with a storage_url exists, the unified batch branch substitutes it so providers like Vertex receive a real gs:// path instead of the opaque token; every other path behaves exactly as before. Verified live that non-managed, managed-owner, multi-model load-balanced, and missing-row requests are byte-identical to base		2026-07-24 18:42:48 -07:00
..
__init__.py	test(batches): add 1:1 test file scaffold for batches component paths (#30529)	2026-06-29 09:22:58 +05:30
test_endpoints.py	refactor(proxy/batches): make managed-file resolution purely additive, fall back like base (#34584)	2026-07-24 18:42:48 -07:00