[ErrorProne] Enable EmptyCatch Error Prone check and document ignored exceptions#37754
[ErrorProne] Enable EmptyCatch Error Prone check and document ignored exceptions#37754stankiewicz wants to merge 2 commits intoapache:masterfrom
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances code quality and clarity by activating the 'EmptyCatch' Error Prone check. This change ensures that any intentionally ignored exceptions are now accompanied by explanatory comments, making the rationale behind such decisions transparent to developers and static analysis tools. The modifications primarily involve adding these clarifying comments to existing catch blocks that were previously empty, alongside the configuration update to enable the check. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
|
Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment |
|
/gemini review |
|
assign set of reviewers |
|
Assigning reviewers: R: @kennknowles for label java. Note: If you would like to opt out of this review, comment Available commands:
The PR bot will only process comments in the main thread (not review comments). |
There was a problem hiding this comment.
Code Review
This pull request enables the EmptyCatch ErrorProne check and adds comments or logging to previously empty catch blocks. The changes are mostly good, adding necessary documentation for intentionally ignored exceptions. However, in a few places, exceptions are silently ignored where logging them would be more appropriate for debugging purposes. I've added suggestions to log these exceptions, which will improve observability without changing the program's control flow.
...twitter/src/main/java/org/apache/beam/examples/twitterstreamgenerator/TwitterConnection.java
Show resolved
Hide resolved
kennknowles
left a comment
There was a problem hiding this comment.
So, on the one hand this keep all behavior the same and enables the check. On the other hand... it leaves all the problems the check is meant to prevent. Overall, LGTM since the value of turning on the check is worthwhile. It would be better if the comments explain why ignoring the exception is the right thing to do.
This PR enables the EmptyCatch Error Prone check and addresses the resulting warnings across the codebase. Empty catch blocks that intentionally ignore exceptions are now documented with clarifying comments.
Changes Included
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.