mirror of
https://github.com/spotipy-dev/spotipy.git
synced 2026-04-26 16:15:51 +03:00
[GH-ISSUE #1084] Offset Glitch #644
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#644
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 @ZachEkstrand on GitHub (Apr 7, 2024).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/1084
Describe the bug
Setting the "offset" arg in the method "current_user_playlists" does not return the list of playlists starting at the correct index.
Giving "offset" the value 42 will start the list at index 42 as expected, however giving "offset" the value 43 will oddly return the list starting at index 42. Any greater number will make it start at the index 1 before.
Your code
This block of code with offset set to 43 has the exact same output:
Expected behavior
current_users_playlists() should start at the correct offset
Output
42. Emo
43. Bren Lukens
44. Jake Ewald
45. Jesse Lacey
46. Summer
47. Kevin Parker
48. Love Songs
49. The Strokes
Environment:
@dieser-niko commented on GitHub (Apr 29, 2024):
It seems to be a problem with the API rather than the library. You could try using the Spotify Web API documentation to check if it's an API issue.
I can't replicate it for myself as I don't have that many playlists in my library.
@dieser-niko commented on GitHub (May 23, 2024):
Any updates so far?
@dieser-niko commented on GitHub (Jul 31, 2024):
Due to the lack of activity, I'm going to close this topic. Please reopen if it's still happening, and try it out in the API documentation as well.