Repository navigation
v0.3.1 — four defects found by using the player, not by testing it
All four were found by operating the player. Three were in code that shipped hours earlier with a fully green suite; the fourth had been there since v0.1.0.
A media key ignored the resume point
The play button resumed where the last session stopped. A media key, or Play from the lock screen, did not — it started the queue from the top and threw the resume point away. Restart Gapless, press play on your keyboard, get the wrong track.
The resume point lived in the GTK front-end, which mpris.rs cannot see. It is a cue on the player now, and play() / play_pause() are the whole of "press play" for the button, media keys, MPRIS and the control API alike.
The control API described a state that had not caught up
POST /api/play answered "track": null about a track it had just started, and POST /api/rating {"stars":N} answered 409 nothing is playing while it was playing. Both read a field set by an event that arrives after the call returns. And is_playing() was briefly false after a successful play, because a GStreamer state change is asynchronous and only the current state was read — so a caller could not tell "starting" from "refused".
A deadlock, caught before release
if let Some(x) = self.cued.lock().unwrap().take() { … } holds the MutexGuard to the end of the body in edition 2021, and the body locked the same mutex. The app stayed alive and MPRIS kept answering while every call timed out with the main loop wedged.
Verification
verify-mpris-modes.sh gains a fourth case: seed a resume point, launch the real app, send Play over MPRIS, and require the cued track. verify-api.sh gains three, one per API defect — the existing 41 walked past all of them, because every scripted check rated by explicit index and read status after a sleep, so nothing ever asked the API a question a person would ask it.
cargo test 30/30 · verify.sh 6/6 · verify-resume.sh 4/4 · verify-mpris-modes.sh 4/4 · verify-api.sh 44/44