Hey everyone!
As we look back at yet another fruitful week in our Community, it’s time to express our gratitude to those who have facilitated insightful discussions and provided invaluable feedback on Sonar products.
Rule Feedback
-
Our thanks to @l0cky3r for helping us identity two improvements for
java:S1764
– a clear rule description (which will come with our extensive updates to all rule descriptions this year) and a fix in case of left-shift. SONARJAVA-4558 -
Next, @paweltichoniuk found a false-negative with
csharpsquid:S1128
when using an inherited properties and namespaces of base classes. SonarSource/sonar-dotnet #7694 was created to enhance our error detection in future releases. -
On the other hand, one of our rules is raising issues where it shouldn’t, and @M_Wtyhk reported a false-positive on
csharpsquid:S2259
, prompting us to create SonarSource/sonar-dotnet #7665 -
@13dagger (spooky name!) reported a false-positive on
php:S1185
that will be tackled in the next development iteration of our PHP analyzer with SONARPHP-1407
General
-
Using the latest version of the SonarScanner for Gradle, @rolgalan_g saw an increase in build time. Your feedback was crucial in identifying areas of improvement on both the analyzer and scanner ends, and this helped us create SONARKT-353 and SONARGRADL-128
-
C/C++ Analysis can be complex, with so much going on at the compiler level. @SSC reported a complex issue now being tracked at CPP-4581.
-
It turns out that the UX for SonarLint for IntelliJ needs to be improved when Power Save Mode is turned on. Thanks @kpise! We’re tracking this at SLI-1039
-
Speaking of Sonarlint for IntelliJ, thanks @tomassurek for helping us pin down SLI-1036
-
@dancook-sl reported an issue that brought a performance/efficiency issue with our Javascript analyzer to our attention. SonarSource/SonarJS #4036 is tracking this improvement!
-
File encoding is… complex. And @avl reported an issue that led us to discover the auto-detection of file encoding isn’t working correctly. SONAR-20012
Delayed Automatic Analysis on GitHub Pull Requests
A change we made on Tuesday resulted in a slowdown for automatic analysis on GitHub PRs, and after community reports from @asafwat, @alexypuli, @raulmarindev, @daniel_norton, and @hisomura, a fix was deployed this morning. We’d like to thank them for reporting their problems and @asafwat for his efforts helping other users experiencing the same problem.
Thanks!
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.