dtourolle
888f0a2a5d
Diagnosed on a device. The likeliest explanation for "audio keeps playing after I leave the player", which is the report this line of work started from. enter_background_audio and exit_background_audio are pure bookkeeping: a boolean and a base offset. Neither confirms the audio stream opened, nor that the webview <video> came back. exit_background_audio's own comment says the element "becomes the player again once it reloads" — a future event nothing waits for, while the flag calls the swap done the moment it is invoked. Foreground the app, then leave the player before the element has reloaded, and the stop is aimed at something that does not exist yet while the audio stream keeps running. The mini player then adopts a live audio session, which is why a movie reappears as an audio track and why it is intermittent. Same defect class as DR-238 … DR-241: state asserted rather than confirmed. It is what Phase::Opening and the open generation exist for — a handoff is an open in flight, and a close during one must cancel it. Today the handoff never reaches an engine as an open at all, which is why close_during_open_never_plays passes on all four engines while the bug survives. Credit where due: the sequence came from the user reproducing it deliberately, not from the logs.
JellyTau
A cross-platform Jellyfin client built with Tauri, SvelteKit, and TypeScript.
Business logic lives in a Rust backend; a UI-rich Svelte frontend handles presentation and talks to it over Tauri's IPC. Targets Linux (libmpv) and Android (ExoPlayer).
Getting Started
This project uses bun as its package manager.
# Activate the Rust environment (fish shell)
source "$HOME/.cargo/env.fish"
# Install dependencies
bun install
# Run in development
bun run tauri dev
# Type-check the frontend
bun run check
# Build for Linux
bun run tauri build
# Build for Android
bun run tauri android build
For the full set of build, test, and Android helper scripts, see scripts/README.md.
Documentation
| Topic | Location |
|---|---|
| Architecture overview & subsystem docs | docs/architecture/ |
| Requirements, traceability & technical debt | docs/requirements.md |
| Build & release process | docs/build/build-release.md |
| Docker builds | docs/build/docker.md |
| Traceability tooling & CI | docs/traceability.md, docs/traceability-ci.md |
| Release checklist | docs/release-checklist.md |
| UX flows | docs/ux-flows.md |
| CI operations (builder image, secrets, runner) | docs/build/ci-operations.md |
Contributing
CONTRIBUTING.md covers the setup, the gates a change has to pass, and the two rules that catch people out (bug fixes start with a failing test; Jellyfin's taxonomy stays in Rust). Please also read the Code of Conduct.
Found a security problem? Do not open an issue — see SECURITY.md.
Verifying a download
Every release publishes SHA256SUMS covering all of its artifacts, plus an SBOM
of what went into the build:
sha256sum -c SHA256SUMS
Desktop builds update themselves from Settings → Updates, verifying each payload against JellyTau's signing key before installing. Android installs are handled by the system installer, so the app links to the releases page instead.
Recommended IDE Setup
VS Code + Svelte + Tauri + rust-analyzer.
License
MIT