Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ref(grouping): Clean up message normalization #53479

Merged
merged 13 commits into from
Jul 25, 2023

Conversation

lobsterkatie
Copy link
Member

This is a refactor intended to make the code handling exception messages in the grouping algorithm a little easier to work with, by adding/clarifying comments and changing names to be more reflective of their namees' respective purposes. The only behavior change is that the hint for message parameterization (shown in the grouping info section of the issue details page) has been changed from Stripped common values to Stripped event-specific values, since the whole point of parameterization is to remove values which different events don't have in common. (All of the snapshot changes are related to this switch.)

The rest of the changes are just renamings, the main theme being to change our language from talking about "trimming" to talking about "normalization," since we both shorten and parameterize the event's message before using it for grouping.

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jul 24, 2023
@codecov
Copy link

codecov bot commented Jul 24, 2023

Codecov Report

Merging #53479 (048dfd7) into master (4a2bbbc) will increase coverage by 0.12%.
The diff coverage is 100.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #53479      +/-   ##
==========================================
+ Coverage   79.42%   79.54%   +0.12%     
==========================================
  Files        4941     4941              
  Lines      208741   208794      +53     
  Branches    35558    35559       +1     
==========================================
+ Hits       165789   166094     +305     
+ Misses      37881    37635     -246     
+ Partials     5071     5065       -6     
Files Changed Coverage Δ
src/sentry/grouping/strategies/configurations.py 100.00% <ø> (ø)
src/sentry/grouping/strategies/message.py 93.10% <100.00%> (ø)
src/sentry/grouping/strategies/newstyle.py 97.26% <100.00%> (ø)

... and 47 files with indirect coverage changes

@lobsterkatie lobsterkatie marked this pull request as ready for review July 24, 2023 23:52
@lobsterkatie lobsterkatie requested a review from a team as a code owner July 24, 2023 23:52
Copy link
Member

@armenzg armenzg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More clarity ❤️ !

@lobsterkatie lobsterkatie merged commit 764039b into master Jul 25, 2023
57 checks passed
@lobsterkatie lobsterkatie deleted the kmclb-clean-up-grouping-message-normalization branch July 25, 2023 16:32
chloeho7 pushed a commit that referenced this pull request Jul 25, 2023
This is a refactor intended to make the code handling exception messages in the grouping algorithm a little easier to work with, by adding/clarifying comments and changing names to be more reflective of their namees' respective purposes. The only behavior change is that the hint for message parameterization (shown in the grouping info section of the issue details page) has been changed from `Stripped common values` to `Stripped event-specific values`, since the whole point of parameterization is to remove values which different events _don't_ have in common. (All of the snapshot changes are related to this switch.)

The rest of the changes are just renamings, the main theme being to change our language from talking about "trimming" to talking about "normalization," since we both shorten and parameterize the event's message before using it for grouping.
@armenzg armenzg added this to the save_event improvements milestone Jul 27, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Aug 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants