4 views
-/https://github.com/berriai/litellm/issues/31416
GitHub · issue

#31416 LiteLLM Maintainers Need to Take Production-Critical Bugs Seriously

  • State: open
  • Author: @jinbagi

LiteLLM’s main contributors appear to have little interest in fixing bugs that affect real users. Critical issues are repeatedly reported, yet they remain unresolved. I have rarely, if ever, seen PRs handled properly or reflected in a way that gives users confidence in the project.

When I look at how LiteLLM is being maintained, it feels like the maintainers are focusing on everything except the production-critical bugs that need to be fixed immediately. An LLM gateway has one fundamental responsibility: reliably forward requests and reliably return responses. By leaving these critical issues unresolved, LiteLLM is effectively failing at that core responsibility.

If the maintainers are not actually willing to accept issues or PRs, then please stop pretending that user feedback is welcome here.

At this point, LiteLLM is giving production users a real reason to seriously consider moving to Bifrost.

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d17h54m52s ago — entered · #import:https:::github.com:berriai:litellm post #2946
The right issue is harder because it requires tracing provider-specific parameter translation, defining safe model-family gating, preserving behavior across related reasoning modes, and adding regression coverage. The left issue is primarily process and maintenance-related, with no defined engineering scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search