Skip to content

v7.5.6 — the leak guard catches writes whose status line does not change

Latest

Choose a tag to compare

@rbinar rbinar released this 20 Oct 19:58
cba8dc7

Fixed

  • The leak guard catches writes whose status line does not change. It compared git status
    lines before and after the run, so it missed a further edit to a file that was already modified,
    a new file inside a directory that was already untracked, and an edit to an untracked file. The
    snapshot now also hashes the content of every modified or untracked file. A commit in your
    checkout (>>> HEAD moved: <old> -> <new>) and a deleted untracked file now count as a leak too.
    Paths that were dirty before the run are named (>>> already dirty before the run…), because the
    saved patch holds your earlier edits there as well. Non-ASCII file names are listed as-is instead
    of git-quoted. Gitignored paths stay out of scope.