Issue Station
Sign In
Tools hereToolbox

litellm - ✅(Solved) Fix [Feature]: [ovhcloud] Migrate fields reasoning_content and duration [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#26586•Fetched 2026-04-28 06:26:41
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
albundy83albundy83
Participants
albundy83albundy83KunalG67KunalG67
Timeline (top)
labeled ×2commented ×1cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #26595: fix(ovhcloud): migrate reasoning_content->reasoning and duration->seconds fields

Description (problem / solution / changelog)

Changes

  • litellm/llms/ovhcloud/chat/transformation.py: normalise new reasoning field to reasoning_content in streaming chunks, with fallback to legacy field during transition window
  • litellm/llms/ovhcloud/audio_transcription/transformation.py: read new seconds field and normalise to duration, with fallback to legacy field during transition window

Relevant issues

Fixes #26586

Pre-Submission checklist

  • I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem
  • I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Screenshots / Proof of Fix

<img width="1911" height="990" alt="Screenshot 2026-04-27 172614" src="https://github.com/user-attachments/assets/549045cf-2ea4-418a-aaf3-bddabfd8442c" />

Changed files

  • litellm/llms/ovhcloud/audio_transcription/transformation.py (modified, +12/-0)
  • litellm/llms/ovhcloud/chat/transformation.py (modified, +10/-4)
  • tests/test_litellm/llms/ovhcloud/test_ovhcloud_audio_transcription_transformation.py (modified, +58/-0)
  • tests/test_litellm/llms/ovhcloud/test_ovhcloud_chat_transformation.py (modified, +73/-0)

Code Example

Bonjour,

Nous souhaitons vous informer d'une mise à jour importante concernant le format de réponse de l'API compatible OpenAI sur AI Endpoints.

Les champs suivants vont être modifiés :

Pour les modèles LLM de type Reasoning qui retournent le raisonnement dans un champ séparé : le champ reasoning_content sera remplacé par reasoning.
Pour les modèles Speech-To-Text : le champ duration sera remplacé par seconds.
Calendrier des modifications :

Le champ seconds est déjà disponible et contient la même valeur que le champ duration.
Le champ reasoning sera ajouté le lundi 27 avril 2026 et contiendra la même valeur que le champ reasoning_content.
Les champs reasoning_content et duration seront supprimés le lundi 11 mai 2026.
Nous vous recommandons vivement de mettre à jour le code utilisant l'API pour migrer vers les nouveaux champs (reasoning et seconds) avant le lundi 11 mai 2026 afin d'éviter toute interruption.

Pour toute question ou retour, notre support technique reste à votre disposition.

Cordialement,

L'équipe IA d'OVHcloud
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

The Feature

Hello,

I have received an ovhcloud notification explaining that the reasoning_content field will be replaced by reasoning for Reasoning models.

And for Speech-To-Text models, duration field will be replaced by seconds but it does not seems to be used in your code.

I attach the mail received from ovhcloud

Motivation, pitch

Here the french mail received from ovhcloud:

<img width="618" height="812" alt="Image" src="https://github.com/user-attachments/assets/af0b82ef-aee6-4bc8-8dd3-8a4c1c6edbfb" />

Here the copy of the text if you want to translate it :-)

Bonjour,

Nous souhaitons vous informer d'une mise à jour importante concernant le format de réponse de l'API compatible OpenAI sur AI Endpoints.

Les champs suivants vont être modifiés :

Pour les modèles LLM de type Reasoning qui retournent le raisonnement dans un champ séparé : le champ reasoning_content sera remplacé par reasoning.
Pour les modèles Speech-To-Text : le champ duration sera remplacé par seconds.
Calendrier des modifications :

Le champ seconds est déjà disponible et contient la même valeur que le champ duration.
Le champ reasoning sera ajouté le lundi 27 avril 2026 et contiendra la même valeur que le champ reasoning_content.
Les champs reasoning_content et duration seront supprimés le lundi 11 mai 2026.
Nous vous recommandons vivement de mettre à jour le code utilisant l'API pour migrer vers les nouveaux champs (reasoning et seconds) avant le lundi 11 mai 2026 afin d'éviter toute interruption.

Pour toute question ou retour, notre support technique reste à votre disposition.

Cordialement,

L'équipe IA d'OVHcloud

What part of LiteLLM is this about?

Proxy

LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

Twitter / LinkedIn details

No response

extent analysis

TL;DR

Update the code to use the new reasoning and seconds fields instead of the deprecated reasoning_content and duration fields to ensure compatibility with the upcoming API changes.

Guidance

  • Review the current implementation of the Proxy feature in LiteLLM to identify where the reasoning_content and duration fields are being used.
  • Update the code to use the new reasoning and seconds fields, which will be available on April 27, 2026, and May 11, 2026, respectively.
  • Test the updated code to ensure a smooth transition before the deprecated fields are removed on May 11, 2026.
  • Consider adding error handling or fallbacks to handle any potential issues during the transition period.

Notes

The exact implementation details may vary depending on the specific codebase and requirements of the Proxy feature in LiteLLM.

Recommendation

Apply workaround: Update the code to use the new fields as soon as possible to avoid any potential interruptions or compatibility issues.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#agent execution#callback error#memory management#API rate limit

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - ✅(Solved) Fix [Feature]: [ovhcloud] Migrate fields reasoning_content and duration [1 pull requests, 1 comments, 2 participants]