-
Notifications
You must be signed in to change notification settings - Fork 471
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
Backend Websocket in modal has a lot of disconnect bugs reports #515
Labels
Comments
I committed some code that should improve the stability. I don't have the credentials thought so I can't test it. Do you mind testing it to see if it performs better? |
Hey, @D1ll4nT happy to review, pls change your PR to Draft PR, and please deploy the backend to your own modal, it should be easier to test that way. |
Assigning to you for the next 2 days @D1ll4nT |
josancamon19
changed the title
Backend Websocket in modal has a lot of disconnect bugs reports ($200)
Backend Websocket in modal has a lot of disconnect bugs reports
Aug 15, 2024
beastoin
added a commit
that referenced
this issue
Aug 27, 2024
…#674) Issue: #515 <!-- This is an auto-generated comment: release notes by OSS Entelligence.AI --> ### Summary by Entelligence.AI - Bug Fix: Improved error handling in the transcription service. We've added a safeguard to ensure that if an unexpected issue occurs during the initiation of a transcription session, the system will now handle it gracefully and close the session properly. This enhancement increases the robustness of our transcription service and provides a better user experience. <!-- end of auto-generated comment: release notes by OSS Entelligence.AI -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
When you deploy the backend to modal, we get a lot of errors as if the Websocket had a lot of issues, but what's happening is a disconnect error, this is mainly a backend task, to make sure the disconnection is handled properly, and the errors in modal are not triggered.
When this is fixed, we should be able to handle gracefully app Websocket disconnections.
The text was updated successfully, but these errors were encountered: