feat(offline): play downloaded video, and drain the offline sync queue (0.4.6)
🏗️ Build and Test JellyTau / Run Tests (push) Successful in 20m34s
Publish Documentation / Build & publish docs to gitea-pages (push) Successful in 6m6s
Traceability Validation / Check Requirement Traces (push) Successful in 18s
Build & Release / Run Tests (push) Successful in 20m26s
🏗️ Build and Test JellyTau / Android Compile Check (push) Successful in 10m3s
Build & Release / Build Linux (push) Successful in 37m59s
Build & Release / Build Windows (push) Successful in 23m0s
Build & Release / Build Android (push) Successful in 40m26s
Build & Release / Create Release (push) Successful in 1m20s

Bundles this session's work plus the concurrent search/offline/player changes.
Every gate passes on the combined tree: 885 frontend tests, 610 Rust tests,
clippy clean, boundary clean, trace coverage 86%.

Offline video playback — four separate defects, each of which alone stopped it:

  DR-133  A completed download's file_path is already absolute (the worker
          rewrites it on completion), but the player rooted it a second time and
          handed the webview /data/user/0/app//data/user/0/app/videos/x.mp4.
  DR-134  The asset protocol was never enabled: no protocol-asset feature and no
          assetProtocol config, so convertFileSrc produced URLs nothing answered.
          Also silently defeated the cached-thumbnail path, which fails soft to
          the server copy and hid it whenever the server was reachable.
  DR-137  Tauri's asset protocol answers a range-less request by reading the
          whole file into memory, and only advertises Accept-Ranges from inside
          its range branch, so the first request never learns ranges exist.
          Chromium gave up with PIPELINE_ERROR_READ after ~31s. Local media is
          now served by a loopback HTTP server: bounded 4 MiB chunks streamed
          from the file handle, every response length-delimited, and a range-less
          request answered with one chunk rather than the file. Confined by a
          per-session token and to the app data directory, because loopback is
          shared between apps on Android.
  DR-138  Release builds set usesCleartextTraffic=false, so Android rejected the
          request to that server before any I/O. A network-security-config
          exempts 127.0.0.1 only; a remote server must still be HTTPS.

Downloads:

  DR-135  download_item never records media_type and the reconnect resolver read
          that NULL as 'audio', so a movie queued from a media card had its URL
          resolved by get_audio_stream_url and completed as an audio-only
          transcode. The item's own type now decides.
  DR-136  Rows already downloaded that way are requeued on reconnect, since
          prevention alone leaves them reading "downloaded" and still unplayable.

Known limitation: a download taken at `original` quality is a byte copy of the
source, so it can be any container. One such file is an AVI holding XVID, which
the webview cannot play in any case — the media server serves it correctly and
Chromium refuses it. That needs either a transcoded download preset or the
native ExoPlayer surface work, and is not addressed here.

Also fixes two ID collisions between concurrent work: DR-143 defined twice
(search vs offline gate) and UT-131 defined twice (Episode Focus hero vs channel
cap). The search requirement is now DR-147 and the channel-cap test UT-141, with
their code references and matrix rows updated.
This commit is contained in:
2026-08-09 16:38:07 +02:00
parent 7b531a40be
commit 1b70926c36
58 changed files with 8130 additions and 2347 deletions
+79
View File
@@ -0,0 +1,79 @@
// Presentation logic for the pending-sync queue.
//
// The queue's *meaning* lives in Rust (which operations exist, how they push,
// when one is abandoned — DR-131). What lives here is purely how a row reads on
// screen: its label, its subtitle, and whether it is currently erroring. Kept
// out of the component so it can be unit-tested, the same pattern as
// episodeStrip.ts.
//
// TRACES: UR-025 | DR-132 | UT-123
import type { SyncQueueItem } from "$lib/api/bindings";
/** How each queued operation reads in the list. */
const OPERATION_LABELS: Record<string, string> = {
report_playback_start: "Playback started",
report_playback_stopped: "Watch position",
update_progress: "Watch position",
mark_played: "Marked as watched",
mark_favorite: "Added to favourites",
unmark_favorite: "Removed from favourites",
playlist_create: "Playlist created",
playlist_delete: "Playlist deleted",
playlist_rename: "Playlist renamed",
playlist_add_items: "Added to playlist",
playlist_remove_items: "Removed from playlist",
playlist_reorder_item: "Playlist reordered",
};
/**
* A human label for a queued operation. An operation this build has no label
* for still reads as something — an unknown row is the case most worth showing,
* since it is the one that will end up abandoned.
*/
export function describeOperation(operation: string): string {
return OPERATION_LABELS[operation] ?? operation.replace(/_/g, " ");
}
/** What the row is about: the item's title if the catalog knows it, else its id. */
export function describeSubject(item: SyncQueueItem): string {
return item.itemName ?? item.itemId ?? "Unknown item";
}
/**
* A row is "stuck" once it has failed at least once — that is what justifies
* showing its error, and what a Retry button acts on.
*/
export function isStuck(item: SyncQueueItem): boolean {
return item.status === "failed" || item.retryCount > 0;
}
export interface PendingSyncSummary {
total: number;
stuck: number;
/** True when every queued row has already failed — retrying needs the server. */
allStuck: boolean;
}
export function summarize(items: SyncQueueItem[]): PendingSyncSummary {
const stuck = items.filter(isStuck).length;
return {
total: items.length,
stuck,
allStuck: items.length > 0 && stuck === items.length,
};
}
/**
* Oldest first — the order they will be replayed in, so the list reads as the
* queue it is. Rows without a timestamp sort last rather than being dropped.
*/
export function sortForDisplay(items: SyncQueueItem[]): SyncQueueItem[] {
return [...items].sort((a, b) => {
if (!a.createdAt && !b.createdAt) return a.id - b.id;
if (!a.createdAt) return 1;
if (!b.createdAt) return -1;
const diff = Date.parse(a.createdAt) - Date.parse(b.createdAt);
return diff !== 0 ? diff : a.id - b.id;
});
}