Skip to content

fix(scripts): a second OBS backup on one day gets its own folder - #46

Merged
DarrellVS merged 1 commit into
devfrom
fix-obs-backup-rerun
Sep 22, 2026
Merged

DarrellVS merged 1 commit into
devfrom
fix-obs-backup-rerun

Conversation

@DarrellVS

Copy link
Copy Markdown
Owner

A second obs-backup.mjs run on the same day copied into the first run's folder and failed its own verification on hashes.json and MANIFEST.txt. It now picks obs-<date>-2, -3, and so on.

Tested: two runs back to back, both "Verified".

🤖 Generated with Claude Code

The folder is named after the date, so a second run the same day copied
into the first one's folder, hashed that run's `hashes.json` and
`MANIFEST.txt` as if they were OBS files, rewrote them, and then reported
both as different: VERIFICATION FAILED on a good backup. Found taking the
backup before running dev against the real library. A run now picks
`obs-<date>-2`, `-3` and so on when the folder or its zip exists.

Two runs back to back: both "Verified".

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@DarrellVS DarrellVS added this to the 3.5.0 milestone Sep 22, 2026
@DarrellVS DarrellVS added bug Something isn't working obs Reads or writes OBS own configuration labels Sep 22, 2026
@DarrellVS DarrellVS self-assigned this Sep 22, 2026
@DarrellVS
DarrellVS merged commit f6f1e0c into dev Sep 22, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working obs Reads or writes OBS own configuration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant