gmusic-playlist
gmusic-playlist copied to clipboard
httplib.IncompleteRead: IncompleteRead(0 bytes read)
My sync script has suddenly stopped working. Not sure if Google have changed something, Debian have pushed out some flakey Python update, or what... I have tried loads of things so far, including a total Python reinstall (which is quite hairy when Debian needs python itself to manage packages).
Logging into google music...
[email protected]'s password:
Traceback (most recent call last):
File "/root/gmusic-playlist/ExportLists.py", line 17, in
Hi mgillespie,
Unfortunately, I am unable to reproduce the issue. It may be a connection issue between you and the google servers. The stack trace you provided indicates it to be some kind of network issue.
When did you first notice the issue and for how long has it continued? Have you tried a different network? What about a different user account?
I looked on gmusicapi's issue list and didn't see any issues like what you mentioned.
Regards
Hi,
I also get this error today when trying to export my playlist for the first time.
@soulfx: Do you think this might be a login issue? Is it possible to get more log entries?
Regards
I'm seeing this same problem on 2x Linux systems (1x Debian wheezy on a RaspberryPI, 1x Linux Mint Desktop PC), there is little in common between them.
It seems like some really bad breaking changes have gone into Python 2.7 with regards to urllib3 and response libraries. Mine is a total disaster zone, even pip doesn't work anymore..
Just installing a clean Debian Jessie (testing) build to see what happens.
Brand new debian install also exhibits the problem.
Hi mg and small,
My searching of gmusicapi's issues for this problem wasn't as thorough as I thought. https://github.com/simon-weber/Unofficial-Google-Music-API/issues/323 - Lists a workaround the for incomplete read issue.
Can either of you try the work around and see if it fixes the issue for you?
Regards
Tried this today, it does eventually time-out and then carry on, but it just moves the problem further on. It sounds like it's a gmusicapi problem at least.
Logging into google music...
Login Successful.
DEBUG:gmusicapi.Mobileclient1:Search(args=['one u2', 1], kwargs={})
Traceback (most recent call last):
File "/root/gmusic-playlist/ExportLists.py", line 43, in
Hi, have finally gotten to the bottom of this. Initially it was a debian problem with their python version, this however changed at some point during my tinkers, into a different problem caused by my Google All Access Subscription that had expired, and I wasn't aware it was a requirement on this script.
Can you add that a Google All Access Active Subscription is a requirement to the project README.md
I guess this can be closed once that's done.
Hi Mark,
Updating the read me to include the prerequisite that an all access subscription is currently required is a good idea.
Feel free to submit a patch to the read me if you get around to it before me.
There may be a way to detect the lack of all access subscription via code, output a warning, and fall back to doing a personal library search only. When I get some time I'll look into it.
I know that one would assume that the export script wouldn't need all access, but there is a portion of the common logic between the export and import script that uses an all access query to determine what the available fields are on track info.
Regards, Soul
I believe the 7b715be80e5756c2222cea19a128086ae20cee7c fixes the index out of bounds issues for non all access accounts. I did a simple test using an account that didn't have all access and it was able to login and run both the import and export scritpts.
Hmm, interesting. This still didn't initially work for me, still coming up with the exception thrown from get_google_track_details().
However I am not in the US, and the curated playlist stuff isn't available here yet. However I signed up for a free US VPN account (I used PrivateTunnel, 500Mb free: https://www.privatetunnel.com/home/?referral=FUXBNWS0PQ ) and since then this has worked, even without the VPN anymore. It's as if logging in from the US at least once is enough to set some kind of flag server-side...