# Sonar Community Roundup, August 30 - September 5

**URL:** <https://community.sonarsource.com/t/sonar-community-roundup-august-30-september-5/148190>\
**Category:** Sonar Updates\
**Created:** [September 5, 2025, 1:04pm UTC](https://community.sonarsource.com/t/sonar-community-roundup-august-30-september-5/148190 "2025-09-05T13:04:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [September 5, 2025, 1:04pm UTC](https://community.sonarsource.com/t/sonar-community-roundup-august-30-september-5/148190/1 "2025-09-05T13:04:04Z")

</div>

Hi all,

Ann took some well-deserved time off for the holiday, so you had just me steering the ship this week (hopefully I didn’t run us aground!).

As always, we want to take a moment to recognize everyone who sparked interesting discussions and gave us valuable feedback to drive continuous improvement.

**SonarQube Server & Community Build:**

- SCIM attribute mapping documentation[proved insufficient](https://community.sonarsource.com/t/scim-attribute-mapping/148003) when @andi encountered user provisioning failures with Entra ID and SCIM. We’ll work on making the docs clearer!

**Rules & Languages Improvements:**

- @mfroehlic raised[great questions](https://community.sonarsource.com/t/java-deprecated-rules/147191) about the interaction between rules `java:S1133` and `java:S6355` for handling deprecated code.[SONARJAVA-5755](https://sonarsource.atlassian.net/browse/SONARJAVA-5755) and[SONARJAVA-5756](https://sonarsource.atlassian.net/browse/SONARJAVA-5756) were created respectively! Thanks for the thoughtful discussion!

- `typescript:S2301` [incorrectly flags](https://community.sonarsource.com/t/typescript-s2301-false-positive/147981) anonymous lambda functions passed as callbacks, as @Fred_D discovered.[JS-854](https://sonarsource.atlassian.net/browse/JS-854) was created to fix this false positive.

- .NET’s `ImmutableArray<T>` initialization gaps[were highlighted](https://community.sonarsource.com/t/immutablearrays-should-be-initialized/147847) by @Corniel, who proposed a new rule to prevent `NullReferenceException`s caused by uninitialized immutable arrays. This has been added to the backlog!

- Jetpack Compose UI declaration patterns[conflict](https://community.sonarsource.com/t/kotlin-s5612-should-adjust-its-behavior-for-function-with-composable-annotations/148135) with `kotlin:S5612`’s 20-line lambda limit, as @Qheb demonstrated. Composable UI hierarchies naturally exceed this limit without being complex logic. A ticket was created to adjust the rule’s behavior for `@Composable` functions.

- A C++ analyzer crash[was thoroughly investigated](https://community.sonarsource.com/t/analyzerexception/147506/) after @neuschwander reported exit code 139 errors. We traced it to a Clang parsing issue with specific bitfield initialization code that actually revealed a subtle bug in the @neuschwander’s code—the crash helped identify problematic aggregate initialization! Great detective work on both sides.

Thank you again to everyone mentioned—and to those we may have missed—for your ongoing contributions in making this community stronger and helping us improve Sonar products.

If you’d like to give a shout-out to someone, whether a community member or a SonarSourcer who helped you, please do so below. And if there’s someone you think we should acknowledge next week, let us know!