Hello Sonar Community!
It’s been a big week here in the Community, with lots of help and guidance from you, our members, to improve our products and your experience with them.
We’re grateful when you take the time to do that, 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:
- Nice to see you @Sebastien_Lesaint, and thanks for letting us know about a little issue in the analysis warnings emitted by our Python analyzer. SONARPY-1846
- @pkubowicz let us know about an irritating stacktrace in his analysis logs. We’ll fix it the next time we work on Kotlin analysis. SONARKT-365
- We updated the GitHub Actions for SonarCloud but forgot to update the docs too. Doh! Thanks @rufer7. We’ll get it fixed.
- @lorant-csonka and @thesrabbit weighed in on the need for some improvements to the color schemes and presentation we use. We’ve registered the needs & will hopefully get to it soon.
SonarLint:
- Thanks @Wajeeh_Ullah for informing us about a bug when a background task is used without a ProgressIndicator or a Job. SLI-1381
- @anon67236913 gave us some feedback about what happens when group policy blocks the JRE bundled with SonarLint – the preferences pane doesn’t get generated at all
We’ll fix this with SLE-861 (and thanks for testing our changes!) - Analysis is supposed to get better in connected mode, not disappear! @ArminOebb let us know that’s exactly what was happening for him in the latest SonarLint for IntelliJ. It’s already fixed for the next release.
Rules & Language Improvements:
- @sodul noticed that
python:S117is raising a false-positive when subclassing is used. Thanks! We’ll fix that with SONARPY-1845 - A Build Wrapper error in probing the compiler causes an empty
build-wrapper-dump.jsonfile and ultimately analysis failure. We appreciate the report, @Jeremy1. CPP-5313 - As a result of @ianbrandt’s report, we’ll improve the detection of Kotlin tests where the class name doesn’t match the file name. SONARKT-389
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.
@ganncamp, @Colin, and @leith.darawsheh