Fatal Error when interrupting OpenAIRealtimeBetaLLMService during speech · Issue #1963 · pipecat-ai/pipecat · GitHub
More Web Proxy on the site http://driver.im/
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
When using OpenAIRealtimeBetaLLMService, a Fatal Error occurs if I start speaking while the bot is still speaking, but only after a function call has previously been executed. I encounter two different erros, see logs below.
Reproduction steps
Use the voice-based OpenAIRealtimeBetaLLMService.
Trigger a prompt that causes the model to make a function call.
Let the bot start speaking the response.
While the bot is still speaking, start speaking yourself (i.e., interrupt via voice).
Observe a Fatal Error.
Expected behavior
No fatal error occurs
Actual behavior
fatal error occurs
Logs
Error 1: A fatal error occurred: ErrorFrame#1(error: The server had an error while processing your request. Sorry about that! Please contact us through our help center at help.openai.com if the error persists. (include session ID in your message: ***). We recommend you retry your request., fatal: True)
Error 2: A fatal error occurred: ErrorFrame#0(error: Error: event_id='***' type='error' error=RealtimeError(type='invalid_request_error', code='invalid_value', message='Audio content of 6100ms is already shorter than 6185ms', param=None, event_id=None), fatal: True)
The text was updated successfully, but these errors were encountered:
pipecat version
0.0.67
Python version
3.13.3
Operating System
macOS 15.5
Issue description
When using OpenAIRealtimeBetaLLMService, a Fatal Error occurs if I start speaking while the bot is still speaking, but only after a function call has previously been executed. I encounter two different erros, see logs below.
Reproduction steps
Expected behavior
No fatal error occurs
Actual behavior
fatal error occurs
Logs
The text was updated successfully, but these errors were encountered: