Skip to content

Harden error handling in Deepgram and MiniMax bridges#2225

Open
chr-hertel wants to merge 1 commit into
symfony:mainfrom
chr-hertel:error-recap
Open

Harden error handling in Deepgram and MiniMax bridges#2225
chr-hertel wants to merge 1 commit into
symfony:mainfrom
chr-hertel:error-recap

Conversation

@chr-hertel

Copy link
Copy Markdown
Member
Q A
Bug fix? yes
New feature? no
Docs? no
Issues -
License MIT

Brings the late-joiner Deepgram and MiniMax bridges up to the v0.10/v0.11 error-handling baseline.

  • MiniMax: adopts HttpStatusErrorHandlingTrait, validating HTTP status before parsing and before streaming (previously it parsed responses blindly, so a 401/429/5xx surfaced as an "undefined array key"). Also guards the async polling/download requests, throws IncompleteStreamException on truncated streams, and uses JsonBodyEncodingTrait for request bodies.
  • Deepgram: adopts HttpStatusErrorHandlingTrait so non-2xx responses raise typed exceptions (AuthenticationException, ServerException, …) instead of a generic RuntimeException, while preserving its richer error-message extraction as a fallback. Also uses JsonBodyEncodingTrait.

Error-path tests added for both bridges. No CHANGELOG entries (bug fix, both bridges unreleased).

@chr-hertel chr-hertel requested a review from OskarStark as a code owner June 22, 2026 23:16
@carsonbot carsonbot added Bug Something isn't working Status: Needs Review labels Jun 22, 2026
@carsonbot carsonbot changed the title Harden error handling in Deepgram and MiniMax bridges Harden error handling in Deepgram and MiniMax bridges Jun 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working Status: Needs Review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants