mirror of
https://github.com/spotipy-dev/spotipy.git
synced 2026-04-26 08:05:55 +03:00
[GH-ISSUE #1157] Running .artist() & .album_tracks() methods are stuck running & won't execute #679
Labels
No labels
api-bug
bug
dependencies
documentation
duplicate
enhancement
external-ide
headless-mode
implicit-grant-flow
invalid
missing-endpoint
pr-welcome
private-api
pull-request
question
spotipy3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotipy#679
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @danisuba10 on GitHub (Aug 22, 2024).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/1157
Describe the bug
After reaching said functions, going a line under with debugger shows nothing, like being stuck in an infinite cycle elsewhere. Going inside, goes into the library's functions, so it gets stuck somewhere there, not in my code.
This happens randomly. Sometimes it works, sometimes not. For some time it works flawlessly, and another time it gets stuck indefinitely. I tried switching Spotify accounts to check if it is a rate limit, but things did not change.
Your code
https://github.com/danisuba10/APIDataGenerator/blob/main/Sources/Generator/AlbumGenerator/AlbumMetadataGenerator.py
Expected behavior
A clear and concise description of what you expected to happen.
Output
No erros, just getting stuck indefinitely.
Environment:
Additional context
Add any other context about the problem here.
@dieser-niko commented on GitHub (Aug 22, 2024):
You have probably hit a request limit. urllib will wait until the limit is gone, but with request limits this can take quite a long time.
If you want to get an error message instead, just do the following:
@danisuba10 commented on GitHub (Aug 22, 2024):
Yes, checking with that option, it returns too many 429 responses. Thanks.
@dieser-niko commented on GitHub (Jan 3, 2025):
Hi @danisuba10, just a quick heads up, we have released a new version (2.25.0) that prints a warning when a limit is reached. I'm not sure if you're still using
retries=0, but if not, this change will warn you when you reach a limit.