Repository navigation
Run parallel local batches with durable attempts and explicit retries - #2
Merged
Merged
Conversation
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.
What changes
Turns the subprocess dispatcher into a parallel, bounded local command queue. SQLite stores individual attempts, ownership, outcomes, exit codes, log paths, retry budgets, and retry due times. Finite JSON batch manifests can be loaded idempotently and resumed after fixing a failed command.
Adds cancellation, explicit retries with bounded backoff, conservative abandoned-attempt recovery, capped stdout/stderr logs, a repository-check and repair example, schema migration, and practical installation and operations guides.
Verification
Scope and limits
The dispatcher stays alive while its commands run. Retries are explicit, and a crashed dispatcher may require operator inspection and recovery. This is a local queue with no distributed leases or exactly-once guarantee. On Python builds without
waitid(WNOWAIT), successful commands must not leave background children running.