mirror of
https://github.com/Googolplexed0/zotify.git
synced 2026-04-24 22:05:53 +03:00
[GH-ISSUE #32] Failed to receive packet #25
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#25
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 @kodenamekrak on GitHub (Jul 22, 2025).
Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/32
Originally assigned to: @Googolplexed0 on GitHub.
When downloading after so many songs it seems to randomly error
@Googolplexed0 commented on GitHub (Jul 22, 2025):
This function usually errors out with "Failed fetching audio key!" when getting API rate limited. "Failed reading packet!" is something different and new. About how many songs did you download before this appeared? Were you using the anti-rate limit config advice from the FAQ?
This second-depth error should be fixed with
f9c9196. This should let you keep downloading more tracks if the primary error occurs again. Please do more large-scale downloads and see if the error occurs multiple times in a row across multiple tracks.@LaneSBarnes commented on GitHub (Jul 28, 2025):
I also got the same "Failed reading packet! Failed to receive packet" error during a bulk download.
I had several successful downloads, then the error happened for one song, and then it continued to successfully download more songs.
I have DOWNLOAD_REAL_TIME set to true so maybe it isn't a rate limit issue 🤔. Its not a big deal though, Ill be able to retry all the failed downloads after the bulk download is done now that you have it skip and continue 👌
Ill lookout to see if it starts happening multiple times in a row. I will also start using --debug
@LaneSBarnes commented on GitHub (Jul 28, 2025):
I saw the error message again, but this time the song successfully downloaded and didnt give a error/stack trace.
I copied this output mid download:
and then the download completed and the output now looks like this:
I see "Failed r" looks like the error message was overwritten a bit.
The song I downloaded plays fine and is complete and has all its metadata correct 🤔
@Googolplexed0 commented on GitHub (Jul 29, 2025):
This may mean the alert is just a nuisance alarm. Probably caused by an unstable connection, but the missing/dropped packets/connection can be requested again. I can mute the underlying logger to stop the popups (see
443ddb5). If you find that one of the songs has been corrupted, please reopen this issue.