Conversation
Command providers that fall through multiple TTS engines sequentially (e.g. paid API -> free API -> local model) can exceed the previous 120s ceiling before a working tier runs, causing the subprocess to be killed mid-synthesis and leaving a truncated audio file. This is a mitigation for NousResearch#50081; a proper idle/progress timeout would be the longer-term fix.
alt-glitch
added
type/bug
Author
This was referenced Jun 21, 2026
Open
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
2 participants
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.
Mitigation for #50081.
Command providers that fall through multiple TTS engines sequentially can exceed the previous 120s ceiling before a working tier runs, causing the wrapper to kill the subprocess mid-synthesis and leave a truncated audio file.
This buys command-provider scripts more headroom while a proper idle/progress timeout is discussed.