Repository navigation
test: pick the cascade tombstone by generation, not row order - #455
Merged
Merged
Conversation
The outbox SELECT has no ORDER BY; CI on main 5cfb5da returned generation 2 before 1, so mine[-1] read the live announcement and failed (run 41005053912, green on re-run). Order-independent now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 30, 2026
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.
test_item_delete_cascades_its_subscriptions_and_still_tombstones(#363) readmine[-1]from an outbox SELECT with no ORDER BY. CI on main5cfb5dareturned generation 2 before 1 and failed (run 41005053912, green on re-run), which blocked #368's deploy until the re-run. Now picks the highest generation. Test-only; no contract path.🤖 Generated with Claude Code