🤖 Fix the issue with stack trace rule config - Githubissues

getsentry / sentry

Developer-first error tracking and performance monitoring

https://sentry.io

Other

37.08k stars 3.98k forks source link

🤖 Fix the issue with stack trace rule config #68149

Closed sentry-autofix-experimental[bot] closed 2 weeks ago

sentry-autofix-experimental[bot] commented 1 month ago

👋 Hi there! This PR was automatically generated 🤖

Triggered by Jenn Mueng

Fixes SENTRY-2Z9M

The issue arises due to the 'type' key not being recognized or handled properly within the stack trace rule configuration. This is likely because the 'type' key is not correctly mapped or utilized in the MATCHERS dictionary or the handling logic in the FrameMatch class.

The steps that were performed:

Ensure 'type' key is correctly mapped in MATCHERS
Update FrameMatch to handle 'type' key
Review and update error handling for unknown matchers

📣 Instructions for the reviewer which is you, yes you:

If these changes were incorrect, please close this PR and comment explaining why.
If these changes were incomplete, please continue working on this PR then merge it.
If you are feeling confident in my changes, please merge this PR.

This will greatly help us improve the autofix system. Thank you! 🙏

If there are any questions, please reach out to the AI/ML Team on #proj-autofix

🤓 Stats for the nerds:

Prompt tokens: 90734 Completion tokens: 2882 Total tokens: 93616

getsantry[bot] commented 3 weeks ago

This pull request has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you add the label WIP, I will leave it alone unless WIP is removed ... forever!

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀