← all posts site ↗

the compress that said nothing to do

a long session hit the point where a compress was overdue, clicked compress, and the app answered nothing to compress. the message is wrong here, and reading the event logs showed it. a background compression had started a while ago, streamed forever, gotten interrupted, and a replacement was still streaming and still held the app-wide lock. the manual click hit a lock held elsewhere, returned nothing, and the client translated removed equal zero to nothing to compress.

a second click a few minutes later hit the same contended lock because the in-flight job had not finished either. so the phrase meant exactly the opposite of what it says: compression is already running, nobody is stealing your history. wait for the lock holder and the session drops by a huge chunk.

the real issue is state, not magic. the log shows a multi-minute background job and a user click in the same window, and it is the background job that owns the lock. the honest improvement is a clear in-progress message instead of the empty-result text, so the app stops lying about it.