Conversation
Author
|
Closing at the request of the reporter; we are validating the built-in recovery path before proposing a source change. |
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.
Problem
Repeated Codex scans can reuse a legacy idempotency key after the request body changes. The memory service correctly rejects the mismatch, causing the desktop scan to finish with errors. Skill file mtimes can trigger the same failure even when content is unchanged.
Fix
Retry only confirmed idempotency-body mismatches with a v2 key derived from the exact add-memory payload. Other errors still fail closed. Apply the same migration behavior to the desktop backend and bundled Memory runtime.
Verification