Fix task status re-entry and verify persisted transitions - #583
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
1 participant
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.
A task returning from
blockedto a previously usedin_progressstatus could report a successful mutation while still reading as blocked. Status writes appended text relations and reused the older value's relation, so a later blocked value continued to win the task reader.Use the existing singleton task-field writer, retain superseded text values and history, and require canonical status read-back before emitting transition/completion effects. The general field editor also forwards the trusted transition actor.
Validation: 61 tests passed across task management and new regressions covering status re-entry, unchanged-state idempotence and failed read-back suppressing completion. This fixes the observed task-completion persistence defect; it does not claim to resolve old remote scheduler deployment divergence.
Tracked in JVNAUTOSCI-2223.