Repository navigation
Conversation
When a live message.updated reuses an id at a new creation time, drop the stale row and insert at the new key instead of leaving duplicates in the session message list.
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
Owner
Author
|
Cleanup disposition: CLOSE_SUPERSEDED — this downstream leaf is byte-equivalent to the same live upstream PR already retained canonically at #163. Keep only that evidence leaf active; this duplicate branch is cleanup-eligible after local reference checks. |
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.
Closes #100
Summary
When a live message.updated reuses an id at a new creation time, drop the stale row and insert at the new key instead of leaving duplicates in the session message list.
Origin (not touched)
anomalyco#51033
Proof
Fail-then-pass on
a message re-sent with the same id keeps one row at the new creation time(negative → green → restore).Policy