You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[bug] speech synthesize --timeout 180 does not terminate stalled audio streaming #309
The command should complete successfully or return a structured timeout within the configured deadline, clearly marking an incomplete WAV as incomplete.
Observed
During a sequential Chinese TTS batch, one invocation remained running for at least 5m43s despite --timeout 180. Its WAV stopped at 540,995 bytes (11.2698 seconds of actual 24kHz mono PCM), far too short for the requested passage. The RIFF/data length fields were streaming placeholders. The parent was reading stdout/stderr via subprocess capture_output, so the output pipe was drained. No actionable error or request ID was available. The stuck child was then terminated; the incomplete audio and checkpoint were retained locally. The service-side billing/completion status is unknown; no claim is made about server cancellation. Re-generating that passage after checking the incomplete file completed normally. This report excludes user text, account information, credentials, internal addresses, and raw logs.
Frequency
Intermittent; a second invocation with the same configuration also stalled and was stopped by an external 240-second deadline. Its partial PCM lasted 13.3951 seconds; other chunks using identical parameters completed. A subsequent invocation completed after a long delay but within the external deadline. No extra paid diagnostic calls were made.
Suggested area to inspect
Whether the configured timeout covers the whole speech streaming/read loop, rather than only connection establishment, and how interrupted streaming output is finalized or flagged.
Activity