# Sonar Community Roundup: May 11 - May 17

**URL:** <https://community.sonarsource.com/t/sonar-community-roundup-may-11-may-17/115552>\
**Category:** Sonar Updates\
**Tags:** weekly-roundup\
**Created:** [May 17, 2024, 2:05pm UTC](https://community.sonarsource.com/t/sonar-community-roundup-may-11-may-17/115552 "2024-05-17T14:05:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [May 17, 2024, 2:05pm UTC](https://community.sonarsource.com/t/sonar-community-roundup-may-11-may-17/115552/1 "2024-05-17T14:05:45Z")

</div>

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](https://community.sonarsource.com/t/small-rendering-issue-in-analysis-warning/114784) about a little issue in the analysis warnings emitted by our Python analyzer. [SONARPY-1846](https://sonarsource.atlassian.net/browse/SONARPY-1846)
- @pkubowicz [let us know](https://community.sonarsource.com/t/noisy-could-not-report-issue-with-code-highlighting-stacktrace-on-every-execution/114979) about an irritating stacktrace in his analysis logs. We’ll fix it the next time we work on Kotlin analysis. [SONARKT-365](https://sonarsource.atlassian.net/browse/SONARKT-365)
- We updated the GitHub Actions for SonarCloud but [forgot to update the docs](https://community.sonarsource.com/t/github-action-versions-in-example-github-actions-workflow-outdated/114132) too. Doh! Thanks @rufer7. We’ll get it fixed.
- @lorant-csonka and @thesrabbit [weighed in](https://community.sonarsource.com/t/feature-request-new-color-scheme-with-more-contrast-in-pr-analysis/112968) 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](https://community.sonarsource.com/t/error-in-sonarlint-for-intellij/114949) about a bug when a background task is used without a ProgressIndicator or a Job. [SLI-1381](https://sonarsource.atlassian.net/browse/SLI-1381)
- @anon67236913 [gave us some feedback](https://community.sonarsource.com/t/sonarlint-for-eclipse-10-1-0-backend-initialization-failed/114983) 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](https://sonarsource.atlassian.net/browse/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](https://community.sonarsource.com/t/sonarlint-file-analyze-not-working-anymore-for-connected-mode/114769) in the latest SonarLint for IntelliJ. It’s already fixed for the next release.

**Rules & Language Improvements:**

- @sodul noticed that `python:S117` is [raising a false-positive](https://community.sonarsource.com/t/false-positive-when-subclassing/115252) when subclassing is used. Thanks! We’ll fix that with [SONARPY-1845](https://sonarsource.atlassian.net/browse/SONARPY-1845)
- A Build Wrapper error in probing the compiler causes [an empty `build-wrapper-dump.json` file and ultimately analysis failure](https://community.sonarsource.com/t/the-build-wrapper-dump-json-file-was-found-but-0-c-c-objective-c-files-were-analyzed/114953). We appreciate the report, @Jeremy1. [CPP-5313](https://sonarsource.atlassian.net/browse/CPP-5313)
- As a result of @ianbrandt’s [report](https://community.sonarsource.com/t/why-please-make-sure-your-sonar-junit-reportpaths-property-is-configured-properly/114544), we’ll improve the detection of Kotlin tests where the class name doesn’t match the file name. [SONARKT-389](https://sonarsource.atlassian.net/browse/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](https://community.sonarsource.com/u/ganncamp), [@Colin](https://community.sonarsource.com/u/colin), and [@leith.darawsheh](https://community.sonarsource.com/u/leith.darawsheh)