Sonar Community Roundup, July 5 - July 11

Sonar Updates
1

Hi everyone,

Live from Berlin at the WeAreDevelopers conference! It’s been a fantastic week connecting with our users and gathering valuable feedback.

As always, we want to take a moment to recognize those who sparked insightful discussions and helped us improve Sonar products.

SonarQube Cloud:

  • Multiple users (@Jed, @keipa) noticed a mysterious “+” character being added to the organization parameter in API calls, resulting in 404 errors. This was due to an extra space in the organization configuration, which got URL-encoded. Thanks for your attention to detail on this subtle but impactful issue!

  • @afmjr and @John_Economidis reported 404 errors when the scanner tried to access /api/v2/analysis/active-rules. The root cause was trailing slashes in the sonar.host.url configuration, which led to incorrect API path construction—an issue with the SonarQube Cloud Service Connection default in Azure DevOps. The team has since released a fix. Thank you for your swift reports!

  • @alexmo and @aaron-fp discovered a serious performance regression in the .NET analyzer, causing build times to increase drastically. The team responded quickly, rolling back changes while investigating. Thanks for your rapid feedback!

Rule & Language Improvements:

  • @f-delahaye requested more flexibility with rule java:S115, which enforces UPPER_SNAKE_CASE for enum constants. They suggested allowing PascalCase for readability. The team agreed and has begun work to make enum constant naming configurable (SONARJAVA-5676). Thank you!

  • @furti discovered that the Web:MouseEventWithoutKeyboardEquivalentCheck rule was incorrectly flagging Angular Clarity’s clr-button components. We’ve created SONARHTML-304 to address this.

  • @outage7652 encountered a StackOverflowError when analyzing a large Java project but there was no log indicating which file caused it. SONARJAVA-5681 was created to fix this. Thanks!

Thank you to everyone mentioned here—and to those we may have missed—for your continued contributions to our community. If you’d like to shout-out someone (community member or SonarSourcer) who helped you, please do so below. Let us know if there’s someone we should acknowledge next week!

4 Likes