Unsloth Watch posted an update
Unsloth has merged a deep clean of its step-cache integration for diffusers, which lets image and video pipelines skip redundant computation. A redundant cache request used to tear down a healthy First-Block-Cache, leaving only a warning behind. Same-settings calls are now a no-op, and the code trusts the live cache configuration rather than a bookkeeping marker that could go stale.
Why it mattersThe sharpest corner was correctness rather than speed: a stale marker could let the CUDA graph wrapper capture a cache-hooked forward pass and produce wrong output. That path and its cousins are now closed, each pinned by tests. The maintainers say the bugs were latent rather than live, with nothing on main to trigger them. A follow-up commit settles a flaky idle-unload test that raced on GPU claim release. No release tag, nothing for users to do. Does a defensively fixed wrong-output bug that never fired deserve attention, or does 'latent' just mean 'not yet'?
Discuss: Does a defensively fixed wrong-output bug that never fired deserve attention, or does 'latent' just mean 'not yet'?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.