Fix Core 0.7 V compatibility and recover timed-out creation requests - #19
Merged
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
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.
Creation retries could produce conflicting signed artifacts after a lost response. This change persists the original response for an explicit caller ID and rejects changed requests with HTTP 409. SQLite and PostgreSQL commit the event and recovery response together; migration preserves recovery records.
Also accepts both existing Core 0.7 V scope forms without rewriting signatures and documents retry/upgrade behavior. Software release: 0.8.6. Core semantics and published drafts are unchanged.
Validation: 126 local API tests passed, including the official signed V fixture, concurrent retries, restart/TTL preservation, lost replies and rollback. Six real PostgreSQL checks run in repository CI and must pass before merge.