You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Make CorpusStorage writes atomic and serialise the read-modify-write in remember()/prune() with a cross-process flock. Without this, two
concurrent writers (e.g. infection --threads=max, parallel CI jobs sharing
a corpus dir) could each read the same on-disk state and the second commit
would silently lose the first; and a process killed mid-write would leave a
truncated JSON document that the next recall() silently drops. Writes now
go through a temp file + atomic rename(), so a reader sees either the
previous or the new document, never a partial one. A short write (full disk)
or a failed rename() aborts the commit and keeps the previous document
intact instead of renaming a truncated temp file over it; a failed flock()
raises instead of silently proceeding unserialised.