#Two stack traces for an error in a React app. Incorrect auto-assigned ownership.

6 messages · Page 1 of 1 (latest)

thorny apex
#

Hi! I have two stack traces in Sentry for a particular event from a React web application. The "JavaScript" stack trace (the stack trace with a JS icon on the left) contains a reference to a "Provider" component that wraps our app. The "React" stack trace (the stack trace with a React icon on the left) however does not contain a reference to the "Provider" component.

The issue is auto-assigned to the owners of the "Provider" component and not to the owners of the component that actually caused the issue. This is undesired behaviour for us — Sentry does know what the offending component is and the React stack trace correctly shows that. But it seems to assign it based on the JavaScript stack trace.

Note: We are using auto-assignments using CODEOWNERS and GitHub.

I would be happy to provide a link to our Sentry error to employees of Sentry if confidentiality is guaranteed.

frail flax
#

Feel free to share a link and we can look at the event to see how this can be improved!

thorny apex
sullen pulsar
#

Hi there! I was taking a look at the issue, and wanted to double check, is there a rule that the 'react' stack trace was meant to have applied to assign to the correct owner?

If not you'll have to add it in your project setting > ownership rules.

If there is, and it's already there you'll need to ensure the ordering is to your expectations. This may involve modifying a CODEOWNERS file since we evaluate top-to-bottom.

Ownership Rules

Learn how to set up ownership rules to automatically assign issues to the right owners.

thorny apex
#

I don't think there is a rule that the "react" stack trace was meant to be used for assigning owners. I did go to Settings > Ownership Rules but I wasn't able to find something that let me specify which stack trace to use.

thorny apex
#

Upgraded our Sentry webpack plugin from v1 to the latest version.