-
Notifications
You must be signed in to change notification settings - Fork 498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Execution Blocked in terminate() Function Due to Infinite Loop in DeepgramTranscriber #699
Comments
+1 faced the same issue |
@akshaysinghas I'm not sure if this project is still maintained |
@cyrilS-dev looks like its not. Any other alternative to this that you have explored? I found this one quite decent in terms of functionality but maintenance is must. Hope community support it or we are working on a wrong project. |
@akshaysinghas I couldn’t agree more that we might be working on the wrong project. I’ve started exploring Pipecat AI, it’s a solid and serious project. Its features are on par with, if not better than Vocode. |
Oh. Cool. Thanks for introducing that to me. I will also explore. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi @cyrilS-dev, I've also been working on Vocode and ran into the same issue - a blocking terminate function for Deepgram (particularly, the receiver function doesn't end). |
Brief Description
In the terminate() function within vocode/streaming/streaming_conversation.py, after the log entry
Terminating events Task
, the rest of the function does not execute. The logs indicate that the loop in DeepgramTranscriber runs indefinitely, preventing further execution.Actual Behavior
The terminate function stalls after attempting to terminate the events task. The Deepgram connection enters an infinite loop of restarts, as shown in the logs.
Relevant Logs:
LLM
None
Transcription Services
None
Synthesis Services
None
Telephony Services
None
Conversation Type and Platform
No response
Steps to Reproduce
Trigger a conversation termination that calls the terminate function.
Observe the logs and note that after
Terminating events Task
, no further log entries are produced from terminate.The logs from DeepgramTranscriber indicate repeated attempts to restart the connection without success.
Expected Behavior
The terminate function should complete its execution, including all tasks such as tearing down the synthesizer, terminating the agent, output device, and workers.
Screenshots
No response
The text was updated successfully, but these errors were encountered: