Aanok/jftui

Next up broken on 0.7.2

Midek opened this issue · 4 comments

Midek commented

jftui version
jftui 0.7.2, libmpv 2.1, libcurl 8.2.1 OpenSSL/3.1.2, yajl 20100

Describe the bug
When entering 'Next Up' in jftui, it displays nothing:

===== megumin =====
D 1: Favorites
D 2: Continue Watching
D 3: Next Up
D 4: Latest Added
D 5: User Views
> 3

===== Next Up =====
>

I have two series that i am in the middle of watching and both show up on jftui 0.6.2

To Reproduce
Run jftui, select 3.. but this might be related to my jellyfin instance only

Expected behavior
Jftui displays series that are currently being watched

I have experimented with different values for "Max days in 'Next Up':" setting in "Display" menu. When i set it to 350, jellyfin webgui also displays nothing. When i set to 0, jellyfin webgui displays garbage (i think it starts to display every series from my media repository). Regardless of that, jftui still displays nothing.

I would appreciate it if jftui could retain old functionality of the "Next Up" menu in jftui, even if its just a configuration parameter or some additional menu.

Aanok commented

Are these shows you're rewatching or is it the first time?

Midek commented

I have not watched them, its new shows that are airing this season

  • 👍1
fullmetal1 commented

This has been happening to me recently as well. None of these series are rewatches
image

Aanok commented

Sorry this issue is going unaddressed for so long. TL;DR: I'll try to update jftui with a rollback to the old behaviour soon.

When I looked into what to do for #39 I took a look at the JF server code that handles NextUp queries and I remember it was very messy (it's still Emby legacy I'm pretty sure). The basic way it works is that it looks through all series in the library, checks the most recently played episode of each one and the episode right after it, if it exists, is the NextUp for that series. Then it filters either by date of view or by count, depending on the query, as well as by allowing rewatching or not.
There's gotta be a bug in there because these results you're seeing (and which I don't, it works tragically fine on my instance) are nonsensical.

The long term solution is to properly look into the server code, find the issue and submit a patch. Which is what I would like to do right away but it's a bit of work (I don't even know C# :P ) and I've been putting it off. We'll just hotfix jftui in the meantime.

  • 👍2