fix(transcription): scale local transcription timeouts with audio duration#1104
Open
xAlcahest wants to merge 1 commit into
Open
fix(transcription): scale local transcription timeouts with audio duration#1104xAlcahest wants to merge 1 commit into
xAlcahest wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Local transcription dies after exactly 5 minutes on long recordings: the local single-request paths hardcode a 300000 ms request timeout (
whisperServer.jsPOST /inference,parakeetWsServer.jstranscribe, llama post-processing, diarization), and the wall is on inference time, so a long file on a slow CPU with a big model gets killed mid-transcription. The newsrc/helpers/transcriptionTimeout.jsscales the timeout with the estimated audio duration (max(300000, seconds * 10000), with a 24-hour ceiling to stay under the 32-bit setTimeout limit) and uses a flat 60-minute cap where duration is not cheaply available, so short dictations keep exactly today's behavior and a genuinely hung server still fails eventually.Fixes #976
Changes