mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #2160] [Bug]: Podcast sync does not properly work #1100
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#1100
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 @vmario89 on GitHub (Oct 27, 2025).
Original GitHub issue: https://github.com/koel/koel/issues/2160
Originally assigned to: @phanan on GitHub.
Read the Troubleshooting guide.
Reproduction steps
Add https://cdn.julephosting.de/podcasts/1355-lanz-precht/feed.rss as Podcast URL in frontend. There are 218 episodes right now. Feed file seems to be valid: https://validator.truefans.fm/?validate=https://cdn.julephosting.de/podcasts/1355-lanz-precht/feed.rss
my Koel instance only shows 190 and stopped in april 2025. i dont know why.
Neither the UI sync button brings error, nor 'php8.3 artisan koel:podcasts:sync' on cli
Expected behavior
sync the full podcast rss feed
Actual behavior
Only partial data is synced
Logs
the log file does not complain about any issue
Koel version
8.1.0
How did you install Koel?
Compiled from source
Additional information
@vmario89 commented on GitHub (Oct 27, 2025):
ps: this already appeared in older versions of Koel, too
@phanan commented on GitHub (Oct 28, 2025):
@vmario89 This is how it looks with my setup:
As you can see, Koel managed to fetch the whole podcast. Maybe there's a memory issue?
@phanan commented on GitHub (Oct 28, 2025):
OK I've managed to reproduce the bug. Will look into it.
@phanan commented on GitHub (Oct 28, 2025):
Actually no. I tried deleting some of the latest episodes, setting the podcast's
last_synced_atproperty to somewhere in the past, and refreshing the podcast – all episodes come back as expected.@vmario89 commented on GitHub (Oct 28, 2025):
but interestingly when i unsubscribe the podcast from web ui, the entry is not dropped in database
@vmario89 commented on GitHub (Oct 28, 2025):
i already unsubscribed and readded the podcast, but there is still an old updated_at timestamp existing and the last_synced_at did not update
@vmario89 commented on GitHub (Oct 28, 2025):
i wonder how it is possible that the database contains the entry, but the gui does not show it aufter unsubscription
edit: ah okay this is caused by dropping an entry in
podcast_usertable@vmario89 commented on GitHub (Oct 28, 2025):
when i run
truncate podcasts;and thenphp8.3 artisan koel:podcasts:syncthe sync runs without errors, but no title is showing up at all@phanan commented on GitHub (Oct 28, 2025):
Truncating
podcastsmeans there's no podcast in your system at all, so it makes sense that nothing shows up.@vmario89 commented on GitHub (Oct 28, 2025):
ah sorry sorry i did not mean
truncate podcasts(this does not work, because foreign key restriction disallows). i diddelete from songs where podcast_id is not null;i thought after clearing a new sync might catch up them all again maybe.@vmario89 commented on GitHub (Oct 28, 2025):
the general doctor log looks okay so far
@phanan commented on GitHub (Oct 28, 2025):
Koel keeps track of the last time a podcast is synced (
last_synced_at). When fetching a podcast, Koel compares itspubDateorlastBuildDatewith thelast_synced_atvalue to determine if syncing should take place. As such, if you want to force a sync, modify this value accordingly.@vmario89 commented on GitHub (Oct 28, 2025):
this does not change it. no reaction on sync, no synced data, no updated last_synced_at timestamp in database after this ation. and no single log entry about success or failure in storage/logs/ :-O
i updated php8.3 to 8.4 in the meantime; no change in behaviour
@vmario89 commented on GitHub (Oct 28, 2025):
could there be any problem regards language or collations maybe?
@phanan commented on GitHub (Oct 28, 2025):
I don't think so.