Bug 491764 - Kasts marks multiple episodes in queue as played when doing a full sync
Summary: Kasts marks multiple episodes in queue as played when doing a full sync
Status: RESOLVED WORKSFORME
Alias: None
Product: kasts
Classification: Applications
Component: general (show other bugs)
Version: 24.05.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: bart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-15 21:22 UTC by benmordecai
Modified: 2024-09-15 03:47 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description benmordecai 2024-08-15 21:22:54 UTC 
SUMMARY
Kasts marks multiple episodes in queue as played when doing a full sync with Nextcloud Gpoddersync backend.

I have marked this as critical since I can't use a program that wrongfully marks episodes played in a silent way. 

STEPS TO REPRODUCE
1. Put 10-15 episodes in queue. 5 of podcast A, 5 of podcast B, 5 of podcast C
2. Play an episode for several seconds or more
3. Refresh podcasts with full sync setting selected

OBSERVED RESULT
1. Podcast stops playing
2. All episodes in queue of podcast A are marked as played and cleared from queue. (Podcast B and C remain untouched)


EXPECTED RESULT
1. Synchronization occurs silently in background.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0 
Qt Version:  6.7.2
Comment 1 bart 2024-08-16 08:13:17 UTC 
Could you please specify enough details in order for us to reproduce the issue?
It's extremely likely that the actual issue is due to a combination of weird or missing data fields in the RSS feed of that particular podcast A.

Proper management of syncing of play positions and play statuses (including merge conflicts) is extremely hard to do correctly even if all the necessary metadata is available.  The current routines are already taking into account many edge cases that were discovered in the wild.
It's likely that you've run into yet another one.  But it can only be solved (hopefully) if there's enough data to reproduce it.

Additionally, do you also have other apps connected to that gpodder-nextcloud instance?  And were they also syncing in between the steps you have mention in your description?
Comment 2 Bug Janitor Service 2024-08-31 03:47:51 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2024-09-15 03:47:05 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.