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

#29539 [Bug]:

  • State: open
  • Author: @cdvankammen
  • Labels: bug, llm translation

### Check for existing issues

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

### What happened?

[Skip to content](https://github.com/BerriAI/litellm/issues/26316#start-of-content) [BerriAI](https://github.com/BerriAI) [litellm](https://github.com/BerriAI/litellm) Repository navigation [Code](https://github.com/BerriAI/litellm) Issues 1.4k (1.4k) Pull requests 2.1k (2.1k) [Agents](https://github.com/BerriAI/litellm/agents?author=cdvankammen) [Discussions](https://github.com/BerriAI/litellm/discussions) [Actions](https://github.com/BerriAI/litellm/actions) [Projects](https://github.com/BerriAI/litellm/projects) Security and quality 8 (8) [Insights](https://github.com/BerriAI/litellm/pulse) gpt-image-2 issue #26316 Closed @wenlong-ihoment Description [wenlong-ihoment](https://github.com/wenlong-ihoment) opened [on Apr 23](https://github.com/BerriAI/litellm/issues/26316#issue-4314361303) Check for existing issues

I have searched the existing issues and checked that my issue is not a duplicate. What happened? When using LiteLLM proxy to call Azure OpenAI gpt-image-2 via /v1/images/generations, the request fails with:

AzureException - { …

Open on GitHub

GitHub resolver

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

Refresh page
vote history (4 events)
#0 of 0 · 31d19h14m45s ago — entered · #import:https:::github.com:berriai:litellm post #1733
-/https://github.com/berriai/litellm/issues/29539⭐3:1-/https://github.com/berriai/litellm/issues/28206
The left issue is harder because it likely requires provider-specific image request translation, Azure compatibility handling, and broader regression coverage. The right issue appears more localized to health-check aggregation or dashboard status logic, with a narrower debugging and testing scope.
#0 of 0 · 31d18h59m37s ago · #import:https:::github.com:berriai:litellm post #1977
-/https://github.com/berriai/litellm/issues/29539⭐5:1-/https://github.com/berriai/litellm/issues/29400
#29539 is harder because it involves diagnosing provider-specific translation behavior and validating compatibility across proxy, Azure, and image-generation paths; #29400 has insufficient detail and appears substantially narrower in scope.
#0 of 0 · 31d18h54m23s ago · #import:https:::github.com:berriai:litellm post #2067
-/https://github.com/berriai/litellm/issues/314675:1-/https://github.com/berriai/litellm/issues/29539⭐
The left requires a cross-cutting, security-sensitive SDK change with provider compatibility review and comprehensive regression testing. The right appears narrower and more localized to a single integration behavior, so it carries substantially less implementation scope and risk.
#0 of 0 · 31d17h57m6s ago — current · #import:https:::github.com:berriai:litellm post #3017
-/https://github.com/berriai/litellm/issues/282358:1-/https://github.com/berriai/litellm/issues/29539⭐
Issue 28235 is substantially harder: it requires coordinated persistence, authorization, accounting, concurrency, and reset-job changes with backward-compatibility risk. Issue 29539 appears comparatively localized to a provider-specific bug path.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search