Hey all,
This week it’s my turn to fly solo while @ganncamp took some well-deserved vacation. Ann and I will finally be a team again next week. 
It has been a slightly muted week here in the Community, but we have still had lots of help and guidance from you, our members, to improve our products and your experience with them.
We’re grateful every time you give us feedback, so like every week we want to spend some time acknowledging everyone who prompted interesting discussions and gave us feedback to help us continuously improve.
SonarCloud:
- @VenkateshG55 and @jesus-gaviria-extern diligently reported issues with the Automatic Analysis of Pull Requests in their organization. This led us to track down a nasty bug where the checkout performed sometimes get an outdated (or missing) commit. Yikes! We’re on the case. Thanks for the reports.
SonarLint:
-
SonarLint hangs when it encounters an illegal character in a file path. Ouch. Thanks for the report, @mBardos76! Let’s fix that with SLVS-1436.
-
@jmini offered us a great report and investigation to help us discover an issue when SonarLint for Eclipse users are using SDKMan. This confuses our JRE auto-detection. Thanks to his report, we created SLE-931.
Rule & Language Improvements:
-
There are some cases where Java’s AutoClosable Interface is obviously not holding resources, and we should make sure those cases don’t trigger
java:S2095(they’re false-positives). Thanks for the feedback @vodoc82730! SONARJAVA-5109 -
Meanwhile,
kotlin:S1172isn’t reporting on public functions when it should (a false-negative). Thanks @HolgerSeith! SONARKT-395 -
@samarpan-b has an idea for a new rule that will raise issues on Javascript/Typescript
awaits inside of loops. We agree this is a good idea! JS-319 -
@kkoop helped us find a parser crash on code with atomics on Microchip XC32. Thanks! CPP-5633
Once more, we extend our thanks to everyone mentioned here - and those we may have missed - for their efforts in strengthening this community and enhancing our Sonar products.
Please leave your own recognitions below – whether for another community member or a SonarSourcer who assisted you this week. If there’s someone you think should be acknowledged in next week’s roundup, don’t hesitate to let us know.