-
Notifications
You must be signed in to change notification settings - Fork 41.2k
fix possible resource leaks #11624
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
fix possible resource leaks #11624
Conversation
@igor-suhorukov Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
@igor-suhorukov Thank you for signing the Contributor License Agreement! |
@philwebb looking at this one, I am a bit surprised about this polish commit. Can you expand why you've removed this call to |
Do you use Continuous Code Quality tools like SonarQube in CI build? |
@snicoll No idea 🤷♂️ It was in 2016. Looks like a mistake. |
@igor-suhorukov We have checkstyle rules but we don't have SonarQube. I've raised #11650. |
* pr/11624: Polish "Fix potential resource leaks" Fix potential resource leaks
This pull request is focused on resolving occurrences of Sonar rule squid:S2095 - Use try-with-resources or close this
I inspect Spring Boot code with sonarcloud.io and found some issues. Try to fix some blocker issues from #11623