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

ActiveJob rescued exceptions should not be reported #537

Closed
stympy opened this issue Apr 11, 2024 · 2 comments · Fixed by #551 or #552
Closed

ActiveJob rescued exceptions should not be reported #537

stympy opened this issue Apr 11, 2024 · 2 comments · Fixed by #551 or #552
Assignees

Comments

@stympy
Copy link
Member

stympy commented Apr 11, 2024

As reported here, we are reporting exceptions that are being rescued via rescue_from, and we shouldn't be.

Front logo Front conversations

@stympy
Copy link
Member Author

stympy commented May 23, 2024

@segiddins I think #551 will fix the problem you encountered with too many reports being sent after you upgraded the gem. If you try the branch, please let me know how it works out for you!

@stympy
Copy link
Member Author

stympy commented May 24, 2024

This fix is available in gem version 5.10.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants