Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LiteLLM exception dumped out when running for the first time #825

Closed
leondz opened this issue Aug 13, 2024 · 1 comment · Fixed by #834
Closed

LiteLLM exception dumped out when running for the first time #825

leondz opened this issue Aug 13, 2024 · 1 comment · Fixed by #834
Labels
cli Command-line interface functions ux Interface & interaction improvements

Comments

@leondz
Copy link
Collaborator

leondz commented Aug 13, 2024

-- litellm exception not welcome

follow clean install instructions, and thenL

$ python -m garak -m test -p lmrc
garak LLM vulnerability scanner v0.9.0.15 ( https://github.com/leondz/garak ) at 2024-08-13T17:39:35.576273
📜 logging to /home/lderczynski/.local/share/garak/garak.log
17:39:38 - LiteLLM:DEBUG: utils.py:147 - Exception import enterprise features No module named 'litellm.proxy.enterprise'
🦜 loading generator: Test: Lorem Ipsum

We don't want to surface Exception import enterprise features No module named 'litellm.proxy.enterprise' (or other LiteLLM green messages)

@leondz leondz added cli Command-line interface functions ux Interface & interaction improvements labels Aug 13, 2024
@leondz
Copy link
Collaborator Author

leondz commented Aug 15, 2024

(garak) 16:26:04 x1:~/dev/garak [feature/topic_probe] $ python -m garak -m test.Blank -p topic.WordnetBlockedWords
garak LLM vulnerability scanner v0.9.0.15.post1 ( https://github.com/leondz/garak ) at 2024-08-15T16:27:19.594279
📜 logging to /home/lderczynski/.local/share/garak/garak.log
16:27:22 - LiteLLM:DEBUG: utils.py:147 - Exception import enterprise features No module named 'litellm.proxy.enterprise'

unable to reproduce stably. this time the message came up once in the middle of a bunch of runs. may be related to running from local dir when package dir isn't set and user cache is the only cache.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli Command-line interface functions ux Interface & interaction improvements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant