Last movie play time keeps increasing

[modem]

Everytime I run Wrapperr, the play time of the last played movie and number of plays keeps increasing. If my last movie was played for 1h, the 1st time I load Wrapperr will show 1 hour, 1 play, the 2nd time I load Wrapper it will say 2 hours, 2 plays and so on.

I have 3 users, I see the issue on 2 users, but not on the other. The only difference I can think of is that the users with the issue played movies in December, while the last time the other user played a movie was in November.

The user that does not show this behavior in movies, is showing it in TV Shows.

[modem]

Maybe the cache was corrupted, I see this in the log everytime I refresh the Wrapperr page:

2024/01/03 10:09:16 New wrap request.
2024/01/03 10:09:16 Checking Tautulli server 'Tautulli'.
2024/01/03 10:09:16 Getting users from Tautulli server 'Tautulli'.
2024/01/03 10:09:16 Getting stats for: User1 User1 195059 [email protected]
2024/01/03 10:09:16 Cache stage completed for User1.
2024/01/03 10:09:16 Checking Tautulli server 'Tautulli'.
2024/01/03 10:09:16 Date 2023-12-07 from server 'Tautulli' marked as incomplete in cache. Refreshing.
2024/01/03 10:09:16 Date 2023-12-12 from server 'Tautulli' marked as incomplete in cache. Refreshing.
2024/01/03 10:09:16 Date 2023-12-22 from server 'Tautulli' marked as incomplete in cache. Refreshing.
2024/01/03 10:09:16 Date 2023-12-23 from server 'Tautulli' marked as incomplete in cache. Refreshing.
2024/01/03 10:09:16 Date 2023-12-29 from server 'Tautulli' marked as incomplete in cache. Refreshing.
2024/01/03 10:09:16 Tautulli refresh/download stage completed.
2024/01/03 10:09:17 Show buddy retrieved.

I deleted the cache file and I don't see the issue anymore, neither these log messages about incomplete cache.

From the logs, I see I started with this incomplete cache message when I updated from v3.2.3 to v3.25. Maybe the cache file got corrupted after the update or there was an change in the cache behavior.

[aunefyren]

Hey, I had this issue recently as well during development. I deleted the cache and it resolved it self. The downside is I have no clue what went wrong in the cache file.

I might create a v3.2.3 instance with a cache and update to v3.25 to see if I can recreate the issue.