Skip to content

Conversation

@lobsterkatie
Copy link
Member

In our grouping algorithm, one of our checks for whether or not to use a given stacktrace is implemented backwards: We claim to ignore a frame if its abs_path isn't a URL, but then only actually do that if its abs_path is in fact a URL.

This will be fixed in the upcoming new grouping config, but in the process of making that change, it became clear that some of our relevant tests are quite hard to reason about. Specifically, we have two grouping snapshot inputs called frame_ignores_module_if_page_url and frame_ignores_module_if_page_url-2, which have a few problems:

  • frame_ignores_module_if_page_url doesn't illustrate what it says it does at all, in that the module isn't in fact ignored. What it does turn out to illustrate is the URL/non-URL frame ignoring bug discussed above.

  • frame_ignores_module_if_page_url-2 does illustrate the module ignoring, but a) its title isn't as clear as it might be, b) it includes a function component, which muddies the waters in terms of what's ignored or not, and c) though it doesn't currently illustrate the URL/non-URL frame ignoring behavior which was previously discussed, once the bug is fixed it will, which will be another thing adding mud to the aforementioned proverbial water.

To fix these problems, this PR adds three new inputs: one to illustrate the module ignoring (and only the module ignoring), and one each to illustrate the URL and non-URL frame ignoring cases, respectively. This should make it easier to see the effects of the bug fix, as only the latter two inputs should be affected.

(A follow-up PR will remove the bad inputs. Doing both in a single PR was confusing GitHub, making it think that things had been renamed and slightly modified rather than replaced.)

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jan 7, 2026
@lobsterkatie lobsterkatie force-pushed the kmclb-clean-up-module-and-single-frame-js-ignoring-tests branch from 1f12942 to 3c08b5a Compare January 7, 2026 20:55
@lobsterkatie lobsterkatie marked this pull request as ready for review January 7, 2026 21:17
@lobsterkatie lobsterkatie requested a review from a team as a code owner January 7, 2026 21:17
@lobsterkatie lobsterkatie merged commit d394bce into master Jan 7, 2026
62 checks passed
@lobsterkatie lobsterkatie deleted the kmclb-clean-up-module-and-single-frame-js-ignoring-tests branch January 7, 2026 21:28
lobsterkatie added a commit that referenced this pull request Jan 7, 2026
This is a follow-up to #105843, which aimed to replace some confusing grouping test inputs with clearer ones. When that PR included both adding the new inputs and removing the old ones, GitHub erroneously detected file renames rather than replacements. That PR was therefore restricted to the file addition half of the process, with the file removal half included here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants