ta
TanStack
GitHub
ai
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
ai
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
test/gemini-tts-e2e
f8aeddbc test(e2e): add Gemini TTS coverage to provider matrix Wire Gemini TTS into the existing E2E test infrastructure. - Add Gemini TTS adapter factory in media-providers - Add Gemini generateContent audio mock - Add Gemini to TTS feature support - Exercise PCM-to-WAV normalization using raw PCM audio responses This extends existing TTS E2E coverage without changing runtime behavior or public APIs.
by Harshdeep ...
H
Succeeded
test/gemini-tts-e2e
f8aeddbc Merge c4ba70db6e757f6b5cbfeba0866da56a4d524f45 into d453647500e33a1412f84a2cc91d486a11265b9b
by Harshdeep ...
H
Succeeded
test/gemini-tts-e2e
63a9e9bc docs: regenerate API documentation (#902) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
by github-act...
g
Failed
test/gemini-tts-e2e
63a9e9bc Merge 0f44d09789e47e77dc784d7383f4a42434f25f7b into f2ded503fcf6c3152d2f5eca0194a8548cd0a9bd
by Harshdeep ...
H
Succeeded
test/gemini-tts-e2e
aa865a91 test(e2e): restore video-gen (gemini) and stateful-interactions matrix entries An earlier upstream merge on this branch botched a conflict in feature-support.ts: it dropped `gemini` from `video-gen` and deleted the `stateful-interactions` entry entirely. Both are silent regressions — `providersFor()` returns `[]`, so those specs generate zero tests — and the missing key also breaks the `Record<Feature, Set<Provider>>` annotation (TS2741), which main's newly added e2e `test:types` gate would fail on. Restore both to match main so the branch's only net change is adding `gemini` to the `tts` matrix, matching this PR's stated scope. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Tom Beckenham
T
Failed
test/gemini-tts-e2e
aa865a91 Merge d6010b92aca900a0ec1724d11bf114b6de6522bf into 084c9e4a64215e352d14ce4f844c641fd5de8326
by Harshdeep ...
H
Succeeded
test/gemini-tts-e2e
c7e4f1cb Merge 637f7e1f9a03bc3e6310c86cf0905ccf8e47d27f into 5deda27085c8785894a28feb5bb3655dbd8f7e0a
by Harshdeep ...
H
Succeeded
test/gemini-tts-e2e
c7e4f1cb feat: add OpenAI diarization support (#651) * add diarization support * fix coderabbit recommendations * refactor: update transcription options and support for diarization - Removed `transcribe-provider-options.ts` file and integrated its options into `transcription-provider-options.ts`. - Updated documentation to reflect changes in response formats, emphasizing the use of `modelOptions.response_format` for diarization. - Enhanced the transcription adapter to handle new model options and response formats, including support for speaker diarization. - Adjusted various components and tests to accommodate the new structure and ensure compatibility with the updated transcription features. * fix coderabbit findings * refactor: update transcription response formats and validation - Removed 'diarized_json' from the allowed response formats in both the server functions and API schemas. - Updated the TranscriptionResponseFormat type to reflect the removal of 'diarized_json'. - Enhanced error handling in the OpenAI transcription adapter to ensure that known speaker names and references are provided together. - Added tests to validate the new requirements for speaker diarization in the transcription process. * fix: address review findings for diarization support - Allow chunking_strategy with non-diarize models (it's a general OpenAI transcription parameter, only *required* for diarize inputs >30s) - Guard the diarized response cast: throw a descriptive error when segments are missing, and always return segments (even empty) for diarized requests instead of silently omitting them - Throw on conflicting responseFormat vs modelOptions.response_format instead of silently preferring the top-level value - Spread modelOptions before model/file and strip stream so untyped passthrough options can't override validated request fields - Surface duration-billed usage on gpt-4o-transcribe-diarize responses instead of discarding it - Guard Number('') in diarized segment id mapping (collided with seg_0) - Move request building inside try so validation errors hit the provider-scoped error log; include offending values in messages - Fix stale/contradictory JSDoc about gpt-4o-* response formats - Docs: correct chunking_strategy framing, document the diarized_json default opt-out and known-speaker pairing rules, add snippet imports for kiira, replace an `as string` cast with a typeof narrow, bump docs/config.json updatedAt - Tests: whisper modelOptions.response_format resolution (verbose_json and text), 4-speaker acceptance boundary, diarized usage/duration mapping (tokens and duration), segment id parsing, empty-segments contract, format-conflict rejection, modelOptions override hardening, missing-segments error Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * ci: apply automated fixes
by 8x4
8
Previous
Next