Repository navigation
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 changed?
Add acknowledged journals for Omes iteration identity, operation recovery and terminal outcomes. Bind Go throughput self-actions to their owning execution, restore frozen starts and operation deadlines after driver restarts, and expose separate probe/scheduler recovery budgets.
Review: Commit by commit, from self-action binding through journal recovery, budget options and fault qualification. This integration includes the open original-start recovery (#539) and scheduler recovery (#542) dependencies.
Why?
A restarted load driver can lose outcomes or regenerate execution state. During intentional faults this can create idle replacement workflows, abandon pending operations or report incomplete counts as a passing failure rate. Recovery needs the same durable record for continuation and acceptance.
How did you test it?
Potential risks
Synchronous journal acknowledgements can reduce offered load; sustained-load and namespace-capacity qualification remain. Ambiguous mutations without proof remain unknown. The journaled worker protocol currently supports Go. The SDK pin and CI build metadata retain the SaaS-compatible Go SDK until its server dependency can adopt the newer version.