Repository navigation
fix(harness): recover from confirmed Continue conflicts [SAP-3292] #1038
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
ynadge
wants to merge
1
commit into
assistant-ui-operation-retries
from
assistant-continue-conflict-recovery
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "@sapiom/harness": patch | ||
| --- | ||
|
|
||
| Allow explicit review and a new continuation after a verified lifecycle conflict while preserving uncertain retries. |
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Lifecycle events suppress conflict recovery
When a lifecycle event precedes the 409 response,
pendingaborts andsetRejectednever records the conflict.Review latest recordstays hidden, leaving the rejected operation on the retry-only path.Learn more
The component aborts its pending request whenever
entry.lifecycle.revisionchanges in the lifecycle-reset effect. A lifecycle transition that causes the server's 409 can also publish the new revision before the POST response reaches the browser. The cleanup then aborts the fetch, and the catch block skips all handling becauseabort.signal.abortedis true. The confirmed conflict therefore never enters the new recovery state.Example: Continue starts at revision 2. End advances the source to revision 3 and its lifecycle event renders first. The effect aborts the POST before its
lifecycle_changedresponse is processed, so the user sees only Retry Continue instead of Review latest record.Recommended fix: Preserve enough operation state to classify the matching 409 despite a source lifecycle render, or stop aborting an in-flight Continue solely because its displayed lifecycle revision changed. Keep navigation, authority, scope, and boot-token abort fences intact, and add a test that publishes the conflicting lifecycle before fulfilling the 409 response.
Was this helpful? React with 👍 or 👎 to provide feedback.