yassin 555e321cf1 fix(router): record flat retry attempts and cap retries from attempted_retries ... Router.log_retry used to copy the failed attempt's kwargs and metadata into metadata.previous_models. Nothing downstream read those copies, but they carried client credentials into spend logs and grew the payload on every retry. Each attempt now leaves a flat record (model group, deployment id, exception type and string, attempt number), which drops RETRY_BREADCRUMB_EXCLUDED_KWARGS and the per-retry credential masking. num_retries_per_request was enforced from len(previous_models), which only looked at the metadata bucket and never exceeded four records. The sync and async client wrappers and the Rust lifecycle guard now read attempted_retries from whichever metadata bucket the call carries. Resolves LIT-7505 Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>		2026-09-13 01:05:51 +00:00
..
ocr	fix(router): record flat retry attempts and cap retries from attempted_retries	2026-09-13 01:05:51 +00:00
support	refactor(ocr): complete native lifecycle and preserve Azure auth (#40734)	2026-09-12 11:56:49 -07:00
conftest.py	refactor(ocr): complete native lifecycle and preserve Azure auth (#40734)	2026-09-12 11:56:49 -07:00
test_ocr.py	refactor(ocr): complete native lifecycle and preserve Azure auth (#40734)	2026-09-12 11:56:49 -07:00