-
Notifications
You must be signed in to change notification settings - Fork 65
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
UTF-8 decoding error parsing protobuf #36
Comments
This should now be fixed, please confirm. |
Yep, that fixed it – though I am now seeing an error on process exit, not sure if this is related: Exception in thread Thread-1 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
File "/usr/lib/python2.7/threading.py", line 505, in run
File "/home/pi/local/lib/python2.7/site-packages/SpotifyWebsocketAPI-0.2-py2.7.egg/spotify_web/spotify.py", line 740, in heartbeat_handler
File "/home/pi/local/lib/python2.7/site-packages/SpotifyWebsocketAPI-0.2-py2.7.egg/spotify_web/spotify.py", line 594, in heartbeat
File "/home/pi/local/lib/python2.7/site-packages/SpotifyWebsocketAPI-0.2-py2.7.egg/spotify_web/spotify.py", line 643, in send_command
<type 'exceptions.TypeError'>: 'NoneType' object is not callable |
FYI, I think the Reply to a MercuryRequest is also another MercuryRequest. Updating to the latest MercuryRequest format and using it for decoding replies works for me with node-spotify-web. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've started to see UTF-8 decoding exceptions being thrown by the google protobuf library when parsing Spotify responses:
Example stack trace below:
The text was updated successfully, but these errors were encountered: