-
Notifications
You must be signed in to change notification settings - Fork 33
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
TransactionFailed uncaught exception #364
Comments
It appears werift is not handling a 438 stale nonce response correctly? I see they handled it in aioice: |
Thanks for the report, werift-ice has a similar problem because it references the old aioice code. I will fix it. |
Awesome, thank you! |
Not trying to rush or be difficult, but curious what the timeline might be for fixing this? I'm still having issues here and want to either catch the exception or the library doesn't throw it. |
I've been busy lately, so a fundamental solution will take time. |
To be clear, we are using TURN function. Maybe we're not implementing it correctly? Either way, thanks for the responses and we'll make do in the meantime! |
I guess I was a bit quick to close this issue- it seems this happens right after a connection is closed, is there any thing I can do in addition to |
@diogeneshamilton 438 error handling is now supported |
Amazing, thank you! I will look out for a new release. |
Hi there @shinyoshiaki 👋 Do you have an idea when you will be releasing this fix? |
@diogeneshamilton @havardholvik released v0.19.2 |
That was fast! Thank you 🙏
…On Thu, May 30, 2024 at 10:57 AM Shin Yoshiaki ***@***.***> wrote:
@diogeneshamilton <https://github.com/diogeneshamilton> @havardholvik
<https://github.com/havardholvik> released v0.19.2
—
Reply to this email directly, view it on GitHub
<#364 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF6CJTCJANS7MREOJCZ45LZE3SYVAVCNFSM6AAAAABCVHLJ4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZGA4DGNJTGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Getting this sometimes, after the connection is open for a while or it tries to reconnect:
Is there any way to prevent this error or catch it so it doesn't crash the server?
The text was updated successfully, but these errors were encountered: