fix(server): silence legacy retained-boundary retraction failures - #26
Merged
Merged
Conversation
- Normalize replayed rollback boundary failures as silent at the projection boundary - Add coverage preserving visibility for unrelated retraction failures
github-actions
Bot
added
vouch:trusted
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.
What Changed
Normalize legacy retained-boundary retraction failures as silent during activity projection, including projection rebuilds, without modifying immutable event history. Added coverage to preserve visibility for unrelated retraction failures.
Why
Older replayed events can contain retained-boundary failures from stale Esc retractions. These failures are no longer actionable and should not appear in the thread feed, while other retraction failures must remain visible.
Checklist