[Server Log] Event Squashing - #63
Draft
ktwrd wants to merge 2 commits into
Draft
Conversation
ktwrd
marked this pull request as draft
June 26, 2026 12:06
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.
Implement Snapshot Event "Squashing" (combining multiple changes into one event being invoked) to reduce the amount of messages sent into a log channel.
This is sadly a side effect of adding support for Member Role/Permission changes. Many things can happen at once, and at the moment, Xenia doesn't smush rapidly done events into one.
With this new implementation, member update changes will be grouped together if they are no further than 5s apart (e.g: if u have an event that happened 6s ago 3s ago and 1s, the middle event would be ignored in the before/after of the event invoked in DiscordSnapshotService)