-
Notifications
You must be signed in to change notification settings - Fork 26
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
runtime error #33
Comments
Hi, I'll have to try the code against new version of the server and maybe newer clients. I'd guess new types of messages have been added which the old code does not handle well? |
I applied the workaround listed in janimo/textsecure-qml#47 (comment) and I confirm that an empty message was received (I debugged the function byte array argument and it was empty). Can the fix be applied? Thanks! |
Please file a PR, and I'll apply it, thanks :)
…On Wed, Apr 26, 2017 at 10:05 AM, Andrea Barisani ***@***.***> wrote:
I applied the workaround listed in janimo/textsecure-qml#47 (comment)
<janimo/textsecure-qml#47 (comment)>
and I confirm that an empty message was received (I debugged the function
byte array argument and it was empty).
Can the fix be applied?
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADD2rTHkGYc-CezLyZNFWnUAHkCeTzhks5rzuysgaJpZM4NH5XM>
.
|
Hello,
I am currently experiencing the following:
panic: runtime error: slice bounds out of range
goroutine 194 [running]:
github.com/janimo/textsecure.handleReceivedMessage(0x0, 0x0, 0x0, 0x555880, 0x10a78040)
.../go/src/github.com/janimo/textsecure/textsecure.go:462 +0xa2c
github.com/janimo/textsecure.StartListening(0x590c68, 0x5)
.../go/src/github.com/janimo/textsecure/websocket.go:204 +0x1e0
Could this be handled cleanly? Also I am not sure what's the cause at the moment, could be connectivity issues but I'm not sure.
The text was updated successfully, but these errors were encountered: