6 views
-/https://github.com/berriai/litellm/issues/30425
GitHub · issue

#30425 [Bug]: Failed to import Prisma client

  • State: open
  • Author: @JokerNoJoke
  • Labels: bug, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

After configuring the database, Litellm encountered an error when starting up. ``` LiteLLM: Proxy initialized with Config, Set models: deepseek-v4-flash 20:48:54 - LiteLLM Proxy:ERROR: utils.py:2873 - Failed to import Prisma client: No module named 'prisma' 20:48:54 - LiteLLM Proxy:ERROR: utils.py:2874 - This usually means 'prisma generate' hasn't been run yet. 20:48:54 - LiteLLM Proxy:ERROR: utils.py:2877 - Please run 'prisma generate' to generate the Prisma client. ```

### Steps to Reproduce

1. I installed using the command "uv tool install 'litellm[proxy]'" as per the document. https://docs.litellm.ai/docs/ ``` uv tool list litellm v1.89.0 - litellm - litellm-proxy ``` 2. config.yaml ``` general_settings: master_key: sk-1234 database_url: "postgresql://postgres:postgres@127.0.0.1:5432/litellm" model_list: - model_name: deepseek-v4-flash litellm_params: model: deepseek/deepseek-v4-flash api_key: sk-xx ``` 3. Specify my configuration at startup `litellm --config ~/config.yaml` 4. Reproduce the error ``` LiteLLM: Pro…

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (7 events)
#0 of 0 · 31d19h14m1s ago — entered · #import:https:::github.com:berriai:litellm post #1628
-/https://github.com/berriai/litellm/issues/30425⭐3:1-/https://github.com/berriai/litellm/issues/20571
The first is harder because it requires diagnosing packaging, optional dependency, and generated-client behavior across installation and startup paths, with greater release and compatibility risk. The second is a localized Helm templating change with straightforward conditional logic and focused chart tests.
#0 of 0 · 31d19h13m58s ago · #import:https:::github.com:berriai:litellm post #1629
-/https://github.com/berriai/litellm/issues/349064:1-/https://github.com/berriai/litellm/issues/30425⭐
#34906 requires tracing and correcting multi-server MCP resource routing while preserving existing aggregation behavior and compatibility; #30425 is comparatively contained dependency/package-generation troubleshooting.
#0 of 0 · 31d19h13m31s ago · #import:https:::github.com:berriai:litellm post #1637
-/https://github.com/berriai/litellm/issues/30425⭐4:1-/https://github.com/berriai/litellm/issues/31953
The Prisma-client failure spans dependency packaging, generation/build workflows, and multiple installation paths, with greater compatibility and deployment risk. The UI redirect issue is comparatively localized to preserving and applying a return path through authentication.
#0 of 0 · 31d19h11m5s ago · #import:https:::github.com:berriai:litellm post #1679
-/https://github.com/berriai/litellm/issues/230055:1-/https://github.com/berriai/litellm/issues/30425⭐
Issue 23005 is harder because it requires profiling and isolating a broad regression across UI rendering, API behavior, and possibly database or asset-loading paths, with unclear reproduction boundaries. Issue 30425 is comparatively contained: dependency packaging, Prisma client generation, and startup validation can be addressed through a focused build or installation change.
#0 of 0 · 31d19h10m31s ago · #import:https:::github.com:berriai:litellm post #1689
-/https://github.com/berriai/litellm/issues/30425⭐3:1-/https://github.com/berriai/litellm/issues/29348
The right issue is harder because it likely requires tracing packaging, dependency inclusion, Prisma generation, and multiple installation/runtime paths, with broader compatibility and release risks. The left issue is comparatively localized to Helm image-tag defaults and chart validation.
#0 of 0 · 31d19h10m8s ago · #import:https:::github.com:berriai:litellm post #1696
-/https://github.com/berriai/litellm/issues/297863:1-/https://github.com/berriai/litellm/issues/30425⭐
The left issue requires extending provider-specific model detection and request translation, with compatibility coverage across Bedrock embedding variants and likely regression tests. The right issue is primarily a packaging or dependency-resolution correction involving the proxy installation path, with a narrower implementation surface.
#0 of 0 · 31d18h39m10s ago — current · #import:https:::github.com:berriai:litellm post #2206
-/https://github.com/berriai/litellm/issues/318325:1-/https://github.com/berriai/litellm/issues/30425⭐
The left task spans frontend architecture, extraction of user-facing resources, locale selection, persistence/configuration, fallback behavior, and ongoing translation workflow. The right task is comparatively localized to dependency packaging, generated artifacts, and startup validation, with a narrower testing surface.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search