Repository navigation
Finish Lot 17: zip update path seen, purge handles read-only folders - #28
Merged
Merged
Conversation
Lot 17's last check: a 0.3.0 zip copy updated from its menu wrote its part to the single log it knows, and the 0.4.0 install-task its shell ran wrote to the dated file. 0.8 s from stop to start. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The real purge of 2026-10-17 took the updates folder but left logs and its parent, empty: the logs folder was read-only, copied back on 2026-09-26 from a OneDrive backup whose folders carry that attribute, and Windows refuses to remove a read-only folder. purge now clears the attribute of an empty folder of its own before removing it, and the after-exit shell passes -Force; a folder that still holds something is left untouched. A real-shell test with read-only folders failed before the change. Lot 17 records it as its last check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lot 17's last two checks, both done on 2026-10-17.
Zip update path. A 0.3.0 zip copy was updated to 0.4.0 from its menu. The 0.3.0 watcher logged to the old single log file. The 0.4.0
install-task, run by the after-exit shell, wrote to the dated file. 0.8 s from stop to start.Real purge. The updates folder was removed. The logs folder and its parent stayed, empty, because the logs folder was read-only: it had been copied back from a OneDrive backup on 2026-09-26, and Windows refuses to remove a read-only folder.
The fix:
purgenow clears the read-only attribute of an empty folder of its own before removing it, and the after-exit shell passes-Force. A folder that still holds something is left untouched. A real-shell test with read-only folders failed before the change and passes after it.Lot 17 is now done: every check has been seen.
🤖 Generated with Claude Code