mirror of
https://github.com/Googolplexed0/zotify.git
synced 2026-04-25 06:15:55 +03:00
[GH-ISSUE #168] struct.error: unpack requires a buffer of 4 bytes #152
Labels
No labels
bug
considering
discussion
documentation
enhancement
enhancement
good first issue
help wanted
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/zotify#152
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 @m335671 on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/168
Originally assigned to: @Googolplexed0 on GitHub.
Zotify Version
Zotify 0.15.6 on the new hierarchy branch
Bug Description
The crash happens at the start of the command right after the logging in step
Bug Triggering Command
`zotify --client-id MY_CLIENTID --persist --save-credentials "True" -rp "/DATA/Media/Music" -q "very_high" -rt "True" --bulk-wait-time 10 --retry-attempts 30 -ie "True" -ip "True" --print-errors "True" --print-api-errors "True" --print-skips "True" https://open.spotify.com/playlist/myplaylistID
Error Traceback / Logs
Config File
Additional Context
I saw someone mentioning this bug in the #143 issue but the person was saying it has been fixed. I hope its not a duplicate and that i'm only doing a bad command... Sorry i'm a newbie so maybe what i'm reporting is not useful or not a bug. ADDITIONAL NOTE: zotify was working with all of these arguments with 2 other playlists while i was on the efficient api branch, I had to switch branch beacause of the error
ValueError: <zotify.api.Track object at 0x7f23f859c3d0> is not in listwhich is also referenced in #143and was marked as fixed in the new-hierarchy branch
@RGPZ commented on GitHub (Feb 11, 2026):
Try run the command again, I get this error every now and then and after a rerun it just works.
@m335671 commented on GitHub (Feb 11, 2026):
Thanks for the reply ! I hope this will be fixed one day...
@Googolplexed0 commented on GitHub (Feb 12, 2026):
Unfortunately, this is an erratic bug within librespot, not this project. Not sure what causes it or how to fix it. See #331.