yucheng 9fa85c5da5 fix(proxy): name the blocking guardrail in x-litellm-applied-guardrails ... When a guardrail hook raises, the common ProxyLogging dispatch (sequential and parallel pre_call, pipeline block, during_call and post_call metrics wrapper, streaming iterator wrapper) now records that guardrail in applied_guardrails before re-raising, and pre_call_hook folds request-declared guardrails in on its raising path. Buffered streams rebuild their response headers after the first chunk so a post_call block reached while buffering carries the blocker too Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>		2026-09-17 08:39:01 +00:00
..
helpers	fix(proxy): keep litellm_call_id on shaped errors and list_batches failure hook	2026-09-16 03:02:50 +00:00
prisma_and_spend	feat(team): team-level model_max_budget with key-level overrides	2026-09-16 00:40:58 +00:00
proxy_logging	fix(proxy): name the blocking guardrail in x-litellm-applied-guardrails	2026-09-17 08:39:01 +00:00
__init__.py	test(proxy/utils): pin bottom-of-file helper behavior (#29509)	2026-06-02 17:45:19 -07:00