You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the LLM_KEY is an empty string, error logs don't make sense.
Example:
class InvalidLLMConfigError(BaseLLMError):
def __init__(self, llm_key: str) -> None:
super().__init__(f"LLM config with key {llm_key} is not a valid LLMConfig")
Example output: skyvern.forge.sdk.api.llm.exceptions.InvalidLLMConfigError: LLM config key with key is not a valid LLMConfig
Possible solutions:
Instead of LLM config key with key, it could log LLM_KEY= is not a valid LLMConfig
Default LLM_KEY can be FILLMEIN
We can handle the empty string/None cases while logging: instead of key {llm_key} is, key {llm_key if llm_key else 'EMPTY_VALUE'} is
The text was updated successfully, but these errors were encountered:
When the LLM_KEY is an empty string, error logs don't make sense.
Example:
Example output:
skyvern.forge.sdk.api.llm.exceptions.InvalidLLMConfigError: LLM config key with key is not a valid LLMConfig
Possible solutions:
LLM config key with key
, it could logLLM_KEY= is not a valid LLMConfig
FILLMEIN
key {llm_key} is
, key {llm_key if llm_key else 'EMPTY_VALUE'} isThe text was updated successfully, but these errors were encountered: