feat(metadocs): single-run flock — nightly job and manual backfill must not race - #30
Merged
Merged
Conversation
…st not race Per-session runs are hours-long during a backfill, so the 21:00 launchd job overlapping a manual run stopped being hypothetical: two runs would race over watermarks and the git repo. flock rather than a pid file — the lock dies with the process, a crash never wedges the nightly job. The yielding run exits 0: the overlap is expected and the other run is doing its work. Co-Authored-By: Claude Opus 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.
Per-session runs are hours-long during a backfill, so the 21:00 launchd job
overlapping a manual run stopped being hypothetical: two runs would race
over watermarks and the git repo. flock rather than a pid file — the lock
dies with the process, a crash never wedges the nightly job. The yielding
run exits 0: the overlap is expected and the other run is doing its work.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com