19 views
-/https://github.com/berriai/litellm/issues/18654
GitHub · issue

#18654 [Bug]: litellm oci gemini model tool call issue

  • State: open
  • Author: @xcke
  • Labels: bug, llm translation, SDK

### What happened?

During Tool call (Steam and also in nonStream) there is an exception when using Gemini models with OCI provider.

### Relevant log output

```shell ... litellm-1 | 14:45:17 - LiteLLM Router:INFO: router.py:1622 - litellm.acompletion(model=oci/google.gemini-2.5-pro) Exception litellm.APIConnectionError: 4 validation errors for OCICompletionResponse litellm-1 | chatResponse.choices.0.message.content.0.OCITextContentPart.text litellm-1 | Field required [type=missing, input_value={'type': 'TEXT'}, input_type=dict] litellm-1 | For further information visit https://errors.pydantic.dev/2.12/v/missing litellm-1 | chatResponse.choices.0.message.content.0.OCIImageContentPart.type litellm-1 | Input should be 'IMAGE' [type=literal_error, input_value='TEXT', input_type=str] litellm-1 | For further information visit https://errors.pydantic.dev/2.12/v/literal_error litellm-1 | chatResponse.choices.0.message.content.0.OCIImageContentPart.imageUrl litellm-1 | Field required [type=missing, input_value={'type': 'TEXT'}, input_type=dict] litellm-1 | For further information visit https://errors.pydantic.dev/2.12/v/missing litellm-1 | chatResponse.choic…

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d18h40m55s ago — entered · #import:https:::github.com:berriai:litellm post #2183
Provider-specific response translation and validation across both streaming and non-streaming tool-call paths creates broader compatibility and regression risk; the dashboard issue is more likely a localized entitlement-check regression.
#0 of 0 · 31d17h55m54s ago — current · #import:https:::github.com:berriai:litellm post #2923
The left issue spans dashboard behavior, authorization rules, budget validation, key creation and update flows, and regression coverage across user roles. The right issue is narrower in scope, centered on provider-specific response parsing and tool-call translation, though it carries some schema and integration risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search