Hey all!
Things slow down at the end of the year, which is often a perfect opportunity for us to catch up on some threads in this Community that need some attention.
We’re grateful every time you give us feedback, 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.
SonarQube Server:
- Big shoutout to @Ruby_Paasche and @acalero for their reports that SonarQube Server v10.8 requires more memory when browsing certain endpoints (listing pull requests and branches). When we compressed the
live_measurestable in SonarQube v10.8, we didn’t consider that some community plugins store a lot of measures, that if loaded at all once in memory can cause anOutOfMemoryexception. SONAR-24057 will be fixed in the next release of SonarQube.
Scanners:
- The Scanner for .NET isn’t picking up configuration from
.editorconfigfiles, but only on some rules? It’s a strange issue we’ll investigate further with SCAN4NET-190. Thanks @lxb!
Rule & Languages Improvements:
-
javascript:S6759takes a fairly narrow view of whether or not a function is a react component, leading to false-negatives. Thanks for the reports @Sti2nd and @Philippe_Formulain! JS-507 -
cpp:S5000may be too broad in applying to C-like structs and C in general, as reported by @giles45. Thanks! CPP-5938 -
Thanks @EdwinOtten for pointing out a code-example for
javascript:S2301that… hasn’t aged well. We’ll clean that up. JS-516 -
java:S2187has a JUnit5 Cucumber runner being detected as a test class without tests, which isn’t right. A fix for SONARJAVA-5262 is already merged. Thanks @pshem! -
csharpsquid:S1172isn’t considering method groups, which leads to false-negatives. Thanks @hankovich! -
java:S2259appears to be raising false-positives, the issue being how nullability annotations are handled in the context of generic types. Thanks for the report @PeerHeijnen! SONARJAVA-5261 -
When searching for TSConfig files, we seem to be traversing hidden directories (like
.git) which shouldn’t be happening. Thanks @ValentinAUCLERC. JS-508
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.
We’ll see you in the new year!