docs: document the treat_finish_reason_as_failure router setting - #1544
Open
paoloantinori wants to merge 1 commit into
Open
paoloantinori wants to merge 1 commit into
paoloantinori wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
BerriAI/litellm#41825 adds the
treat_finish_reason_as_failurerouter setting, and the documentation validation test requires everyRouter.__init__parameter to appear in this table, so that PR's documentation check stays red until this row lands.Scope
One row in the router_settings Reference table in
docs/proxy/config_settings.md.Verification
The row key matches the
Router.__init__parameter name exactly, which is whattests/documentation_tests/test_router_settings.pyin the main repo compares against the table.