Skip to content
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

read_next_message string index out of range #56

Closed
awesomebytes opened this issue Nov 7, 2015 · 6 comments
Closed

read_next_message string index out of range #56

awesomebytes opened this issue Nov 7, 2015 · 6 comments

Comments

@awesomebytes
Copy link
Collaborator

I've seen this error happen from time to time, I cannot reproduce it:

Exception in server.py-read_next_message.
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/remi/server.py", line 177, in read_next_message
    length = self.bytetonum(length[1]) & 127
IndexError: string index out of range
@dddomodossola
Copy link
Collaborator

Hi awesomebytes, this exception happens when the browser disconnects or is closed. This is managed. ;-)

@awesomebytes
Copy link
Collaborator Author

Ok, great to know, next one who googles this will be fine haha

Thank you :)

@buxtonpaul
Copy link

Hi
How do you mean managed? I have this issue on version 1.0 installed from pip.
After disconnecting the browser and receiving the message I am then unable to launch again as the socket is already bound.

Excellent project by the way, looking forward to slapping it onto some raspberry pi's!

@dddomodossola
Copy link
Collaborator

Hello @buxtonpaul .
This exception is not an issue. Is a known 'normal' behaviour caused by browser (websocket) disconnection. This isn't the cause of your problem. Can you provide more info about the problem? Such as host system, web browser and so on...

@buxtonpaul
Copy link

Actually I feel a little silly. This issue made it look like the server had shutdown, however it is still running, which is why when I attempt to run it again it fails. Doh!

@dddomodossola
Copy link
Collaborator

@buxtonpaul no problem, you are welcome ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants