austinried dd6b0ea00c retry a read that lands past a cold transcode ...

A transcoded stream is chunked with no length, so the app declares an upper-bound
length, and on the first request the server is still producing the stream: a seek
near that bound lands past the data and comes back as POSITION_OUT_OF_RANGE
(Navidrome answers 416 until it has cached the transcode). That first request is
what warms the cache, so give the load one retry after a second: the retry sees a
real Content-Length and the stream plays and seeks. Further out-of-range errors
are given up on rather than looped.

2026-10-04 00:30:04 +00:00

..

schemas/com.subtracks.data.db.SubtracksDatabase

search the library through FTS5 trigram tables

2026-10-04 00:30:03 +00:00

src

retry a read that lands past a cold transcode

2026-10-04 00:30:04 +00:00

build.gradle.kts

parse Subsonic dates with java.time via core library desugaring

2026-10-04 00:29:55 +00:00