2025-02-01, 03:16 PM
Hey, thank you for raising the issue!
When I implemented the initial "fix" it seems like I did a wrong assumption on how the pre-fetch works which is now causing these excessive amouts of requests (this should only happen once at the beginning and after that only fetch new entries).
Since I do not have any LiveTV setup myself I was and am flying somewhat blind in testing changes properly. I've pulled up https://github.com/jellyfin/jellyfin/pull/13469 which should a) lessen the amount of requests siginificantly by only fetching for updated and new EPG entries b) recognizing updated and new entries more reliably. I have some people on the team at hand which can test it, but it depends on their availability.
Implementing handling of custom response codes will require more changes which are out of scope for that PR (see the initial fix for what we'd need to change to properly fix these kind of limitations).
When I implemented the initial "fix" it seems like I did a wrong assumption on how the pre-fetch works which is now causing these excessive amouts of requests (this should only happen once at the beginning and after that only fetch new entries).
Since I do not have any LiveTV setup myself I was and am flying somewhat blind in testing changes properly. I've pulled up https://github.com/jellyfin/jellyfin/pull/13469 which should a) lessen the amount of requests siginificantly by only fetching for updated and new EPG entries b) recognizing updated and new entries more reliably. I have some people on the team at hand which can test it, but it depends on their availability.
Implementing handling of custom response codes will require more changes which are out of scope for that PR (see the initial fix for what we'd need to change to properly fix these kind of limitations).