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
During a process handover, deferred recovery could mark a job started by the successor as interrupted even while its assistant was still running. Execution history already respected the process start cutoff, but the job's status did not, producing contradictory state and potentially a false failure notification. Apply the same cutoff to job occurrences before saving an interrupted result. Legacy occurrences with no start timestamp are still recovered.
Scope
Compatibility
No schema, API, dependency, or runner-protocol changes.
Validation
go test ./internal/schedule -count=1.git diff --check.Safety