-
Notifications
You must be signed in to change notification settings - Fork 959
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
Spotipy hangs, no errors #844
Comments
I'm having the same issue. No errors, the code just hangs when doing spotipy calls. |
i'm also having the same issue in Google Colab link to notebook Update: i was previously using |
Check if you are not getting a 429 error (too many requests per Spotify client ID). |
Let's continue this discussion in #913 |
Describe the bug
There is an issue with logging and exception handling.
Your code
To recreate this I just used one of the examples from the documents:
Simply passing in some valid credentials and seeing if I can get albums from an artist. I ran this in a loop 10-20 times in a short period of time, with my app in developer mode.
After much digging, I was able to track the problem down by stepping through some functions until I got to the actual GET HTTP request. I looked at the payload, extracted the token, and checked if it was valid. It was not.
I'm in developer mode, without a quota extension. I believe the issue is actually stemming from this rate limit. I've waited a couple days, the problem resolved itself but then after a few calls it came back. Is there an error with the callback that's not returning the 429 error expected here?
Expected behavior
I expected to get a list of albums from this artist but that didn't happen.
Output
Probably the most frustrating of all is that it just hangs. There's no callback saying the token is invalid, or a rate limit has been exceeded, it just spins and spins. The warning expected from Spotify would actually be very helpful. It'll say how long we need to wait until we should execute another HTTP request.
Environment:
The text was updated successfully, but these errors were encountered: