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

Rescue all error classes in TracePoint block #3

Conversation

davidrunger
Copy link
Contributor

@davidrunger davidrunger commented Aug 23, 2024

fixes #1

Also fixes the error mentioned here (currently occurring on main): #2 (comment)

@davidrunger
Copy link
Contributor Author

davidrunger commented Aug 23, 2024

The change proposed in this PR might or might not be a good idea, so feel free to reject it. I think that the main risk/downside is that, by rescuing all error classes (and also not even logging that an error occurred), we might swallow errors that we actually want/need to know about. But it does fix the current test failures on main, and I think it will also fix the issue #1 that I reported.

@skryukov
Copy link
Owner

Thanks for diving in, @davidrunger! I'll try to check this over the weekend 🙏

@davidrunger
Copy link
Contributor Author

Closing in favor of #4.

@davidrunger davidrunger deleted the rescue-all-standard-errors-in-tracepoint-block branch August 26, 2024 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants