fix: raise clear error when ALIAS_API_KEY is missing for alias models. #450
Open
initpwn wants to merge 1 commit into
Open
fix: raise clear error when ALIAS_API_KEY is missing for alias models. #450initpwn wants to merge 1 commit into
initpwn wants to merge 1 commit into
Conversation
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.
When an alias model such as alias1 or alias1-fast is used without setting ALIAS_API_KEY in the environment, the fallback placeholder value "REDACTED_ALIAS_KEY" is applied. This causes a 401 error from LiteLLM:
LiteLLM Virtual Key Expected. Received=REDA***_KEY, expected to start with 'sk-'Fix: Fail fast if ALIAS_API_KEY is not set in env when alias model is selected.
Related: #351