Skip to content

v2.0.1 - read-only-fs regression-test fix

Choose a tag to compare

View all tags
@HetCreep HetCreep released this 25 Jul 04:09
v2.0.1
This tag was signed with the committer’s verified signature.
HetCreep
SSH Key Fingerprint: 0osv9sipbbl2qmrI00rRA3kcEKs4ZuS+FBihPD/c8DU
Verified
Learn about vigilant mode.
9263ffd
This commit was signed with the committer’s verified signature.
HetCreep
SSH Key Fingerprint: 0osv9sipbbl2qmrI00rRA3kcEKs4ZuS+FBihPD/c8DU
Verified
Learn about vigilant mode.

PATCH - CI-green fix-forward for v2.0.0. Test-only; no shipped-code change.

Fixed

  • The read-only-journal regression test now simulates a true read-only fs on every platform. v2.0.0 routed markResumed through the atomic writer (per-pid temp + rename); the test chmod-ed only the journal FILE 0o444, which on POSIX rename(2) replaces needing only DIRECTORY write - so the temp renamed over the read-only file, the write succeeded, the "may repeat" honesty note never fired. Green on Windows (MoveFileEx refuses a read-only destination) but red on macOS/Linux. The test now also chmods the containing DIR 0o555 and restores perms in finally - the honesty path is exercised on every platform, no skip. The v2.0.0 atomic markResumed is unchanged and correct.

(Release note corrected 2026-07-25: the earlier backfilled body described v2.0.2's sandbox-realpath topic - a cross-attribution caught by the room reviewer's R9 audit; this body now matches CHANGELOG [2.0.1] verbatim-in-substance.)

Assets 2
Loading