Optional count fields added#76
Merged
Merged
Conversation
neSpecc
reviewed
Jun 1, 2026
| payload: CatcherMessagePayload<Type>; | ||
|
|
||
| /** | ||
| * Number of identical occurrences this message represents. |
Member
There was a problem hiding this comment.
Suggested change
| * Number of identical occurrences this message represents. | |
| * Number of identical occurrences this message represents. Computed on Catcher side to dedupe similar events caused in the same time. |
Reversean
force-pushed
the
feat/catcher-message-count
branch
from
June 24, 2026 13:23
9c0336f to
92c6026
Compare
neSpecc
approved these changes
Jun 25, 2026
Kuchizu
approved these changes
Jun 29, 2026
Adds an optional count field used by the client-side debounce feature to merge repeated occurrences of the same error within a short time window into a single network message, while still tracking how many real occurrences it represents. - CatcherMessage.count — set by Catcher SDK on the message sent to Collector - RepetitionDBScheme.count — set by the grouper worker on the stored repetition, carrying the same number through to API/Garage Both fields are optional; absent or 1 means a single occurrence — no behavior change for clients/data that don't use debounce.
Reversean
force-pushed
the
feat/catcher-message-count
branch
from
June 29, 2026 07:44
c9afac3 to
fb6ed27
Compare
Reversean
changed the title
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
3 participants
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.
Adds an optional
countfield used by the client-side debounce feature to mergerepeated occurrences of the same error within a short time window into a single
network message, while still tracking how many real occurrences it represents.
CatcherMessage.count— set by Catcher SDK on the message sent to CollectorRepetitionDBScheme.count— set by the grouper worker on the stored repetition,carrying the same number through to API/Garage
Both fields are optional; absent or
1means a single occurrence — no behaviorchange for clients/data that don't use debounce.