GO-3924: Fix event message ordering for state change events #1561
Conversation
This file contains 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
KirillSto
reviewed
Sep 9, 2024
| @@ -686,6 +686,8 @@ func (s *State) apply(fast, one, withLayouts bool) (msgs []simple.EventMessage, | |||
| } | |||
|
|
|||
| msgs = s.processTrailingDuplicatedEvents(msgs) | |||
|
|
|||
| sortEventMessages(msgs) | |||
There was a problem hiding this comment.
It seems we should insert sorting before trailing dups analysis. Or we don't need this analysis at all? 😀
fat-fellow
approved these changes
Sep 9, 2024
KirillSto
approved these changes
Sep 9, 2024
deff7
deleted the
go-3924-convert-empty-object-to-set-messages-order-problem
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
No description provided.