Skip to content

fix: refresh transient availability metadata on explicit retry - #3291

Draft
SonAndE14 wants to merge 1 commit into
recloudstream:masterfrom
SonAndE14:contrib/availability-cache-retry
Draft

SonAndE14 wants to merge 1 commit into
recloudstream:masterfrom
SonAndE14:contrib/availability-cache-retry

Conversation

@SonAndE14

Copy link
Copy Markdown

Shorten caching of comingSoon metadata to thirty seconds while retaining the normal ten-minute cache. Explicit retry invalidates the matching cached response before loading it again. Explain that missing playable content can be unavailable or upcoming instead of asserting a future release, and make the message retryable on TV and phone.

Also keep the rolling response cache within its configured capacity and propagate caller cancellation through link extraction while returning false for the extraction deadline. This does not manufacture episodes, links or playable media and does not claim to repair failed extensions. A genuinely future title remains non-playable.

Cache-policy regression tests cover the two lifetimes and clock rollback. Real transient-provider states and TV retry focus still require device QA.

Validation: :library:checkKotlinAbi, :app:testPrereleaseDebugUnitTest, and :app:assemblePrereleaseDebug passed locally. 10 JVM tests passed without failures or errors. Lint is left to this PR's GitHub workflow; the complete integration branch previously passed Lint. These results are not physical-device validation.

AI disclosure: implementation, code review and automated test execution used OpenAI Codex assistance, as required by AI-POLICY.md. This draft submits the implemented work for human review; pending physical checks and limitations above are not claimed complete. No changes to provider source code or the projector launcher are included.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants