Add FunASR/SenseVoice API backend - #1554
Conversation
|
Follow-up for head
Current local verification is green: 13 focused FunASR tests, 96 recording-widget tests, and the broad repository suite ( The new CI and Snapcraft runs are both |
|
Summer is busy time, but sure, I will review this. |
…uthor-blockers # Conflicts: # buzz/transcriber/recording_transcriber.py
|
Refreshed this PR onto current Conflict resolution kept the upstream Validation on exact head
GitHub now reports the PR |
Signed-off-by: LauraGPT <18321252+LauraGPT@users.noreply.github.com> # Conflicts: # docs/docs/index.md
Signed-off-by: LauraGPT <18321252+LauraGPT@users.noreply.github.com>
Summary
FunASR APImodel backed by a separately running FunASR/SenseVoice OpenAI-compatible serverfunasrapiCLI model typeBoundary fixes
FUNASR_API, matching the existing OpenAI API behaviorTypeErroror discard the transcripttimestamp_granularitiesfields that the FunASR endpoint does not supportCurrent-main refresh
main@3fa37a9d5238d29fa75a66cdb76555fd2820957ewithout rewriting the already reviewed feature history2b77a03619d6ccd9159be70f348bec0b78b6b8edVerification
RecordingTranscriberwas called 0 times; it now starts once with the expected API optionsTypeError: 'NoneType' object is not iterable; it now returns the complete text fallback and sends no word-timing request323 passed1134 passed, 7 skippeduvlock check withuv 0.12.1, Python 3.12, Transformers 5.14.1, and Torch 2.8.0+cu129git diff --checkGitHub currently reports the PR mergeable with no unresolved review threads. The exact-head CI and Snapcraft workflow runs are
action_requiredwith zero jobs, so they require upstream approval before GitHub can execute them. The prior and refreshed heads are retained oncodex/backup-buzz-1554-086a241-20260803andcodex/backup-buzz-1554-prepush-2b77a03-20260803in the contributor fork.Closes #1140