Repository navigation
fix(harness): reconcile uncertain Assistant Resume commits [SAP-3292] #1024
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-compaction-provenance
from
assistant-resume-commit-reconciliation
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 | ||
| --- | ||
|
|
||
| Report uncertain Assistant metadata commits and reconcile exact Resume execution state. |
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.
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.
🟡 Cleanup masks unconfirmed commits
When temporary-file removal fails after uncertain publication,
writeAssistantJsonreplacesAssistantStorageCommitUnconfirmedErrorwith the cleanup error. Callers cannot identify and reconcile the possibly committed operation.Learn more
A rejection from an awaited
finallyblock replaces the error already thrown by itstryorcatch. Here, storage has already published the destination and failed to confirm rollback. Another filesystem failure duringfs.rmtherefore removes the only signal that the commit is uncertain. This is especially reachable during the same degraded-storage condition that caused publication or rollback to fail.Example: The destination rename succeeds, directory sync fails with
EIO, rollback also fails, and removing.rollbackthen fails withEIO. The caller receives the removal error withoutASSISTANT_STORAGE_COMMIT_UNCONFIRMED, although the new generation remains readable.Recommended fix: Make temporary cleanup best-effort when an earlier error is pending, or capture cleanup failures without replacing
AssistantStorageCommitUnconfirmedError. Preserve cleanup failures only when no primary operation error exists.Was this helpful? React with 👍 or 👎 to provide feedback.