# Sonar Community Roundup, March 2 - March 8 **URL:** \ **Category:** Sonar Updates\ **Tags:** weekly-roundup\ **Created:** [March 8, 2024, 4:57pm UTC](https://community.sonarsource.com/t/sonar-community-roundup-march-2-march-8/110771 "2024-03-08T16:57:01Z")\ **Posts on this page:** 4\ **Page:** 1
**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:** [March 8, 2024, 4:57pm UTC](https://community.sonarsource.com/t/sonar-community-roundup-march-2-march-8/110771/1 "2024-03-08T16:57:01Z")
Hello Sonar Community! Like every week we want to spend some time saying thanks to everyone who prompted interesting discussions and gave us feedback on Sonar products that will help us continuously improve. **SonarQube:** - Thanks @torsten.stach for [letting us know](https://community.sonarsource.com/t/portfolio-download-url-ignore-the-property-sonar-core-serverbaseurl/110111) that in SonarQube v10.4, the value of `sonar.web.context` isn’t being taken into account when generating the Portfolio Report PDF. [SONAR-21772](https://sonarsource.atlassian.net/browse/SONAR-21772) - @Carsten_HB is one of many users over the years who’ve reported [issues flickering between open and closed statuses](https://community.sonarsource.com/t/issue-keeps-on-switching-between-statuses-without-any-relevant-changes/98934). It’s been something of a wild goose chase for us - never getting close enough to actually identify the problem. Finally, though, we’ve [tracked it down](https://sonarsource.atlassian.net/browse/SONAR-20695). (Roast goose for dinner!) **SonarCloud:** - Being called out for your mistakes is one thing. Being called out for someone else’s is something else entirely. And we’ve been doing that for a while, as @Luiz_Soares [pointed out](https://community.sonarsource.com/t/not-using-sonar-exclusions-but-getting-deprecation-warning/109974) because under some circumstances the SonarScanner for .NET adds deprecated properties to the analysis context. Apologies to everyone who’s gotten the (unwarranted) deprecation warnings. We’ll fix it with [sonar-scanner-msbuild#1888](https://github.com/SonarSource/sonar-scanner-msbuild/issues/1888). **SonarLint:** With the release of - SonarLint for Eclipse 10.0 - SonarLint for IntelliJ 10.4 - SonarLint for VSCode 4.4 we have almost completely refactored each plugin. We spent the last several weeks manually testing everything and fixing bugs, but we knew there was a possibility users would face a few problems. We see the bug reports you’re turning in, and we’re grateful for them. We should have updates on them soon. **Language & Rule Improvements:** - Our trusty COBOL expert @Jos_Abrahams [let us know](https://community.sonarsource.com/t/fp-on-rule-cobol-s1966-when-moving-an-alpha-field-to-a-numeric-field-with-conversion/109050) about a false-positive on `cobol:S1966` when moving an alpha field to a numeric field with conversion. Thanks Jos! [SONARCOBOL-1698](https://sonarsource.atlassian.net/browse/SONARCOBOL-1698) - Jos also [discovered](https://community.sonarsource.com/t/wrong-file-reported-when-issue-is-found-on-cobol-s1764/109763) that issues found by `cobol:S1764` are only being reported in the copy member, not the source file. [SONARCOBOL-1699](https://sonarsource.atlassian.net/browse/SONARCOBOL-1699) - Thanks @kdebisschop[for identifying a false-positive](https://community.sonarsource.com/t/false-positive-with-php-strtok/109807) with `php:S2201`, mistakenly raising an issue saying that `strtok()` has no side effects. [SONARPHP-1490](https://sonarsource.atlassian.net/browse/SONARPHP-1490) - As [reported by](https://community.sonarsource.com/t/sonarlint-vs2022-cpp-system-argumentoutofrangeexception/108097) @toshihiro_hayashi, our C and C++ analysis only supports files with UTF-8 encoding. We’ve created [CPP-5066](https://sonarsource.atlassian.net/browse/CPP-5066) to track interest on supporting other file encodings. - Lines of Javascript code that just declare exported members should not be considered executable lines (that can be covered by tests). Thanks for the [nudge](https://community.sonarsource.com/t/javascript-typescript-exporting-const-included-in-executable-lines-for-coverage/106830) @denis_gillespie! [SonarSource/SonarJS #4592](https://github.com/SonarSource/SonarJS/issues/4592) - Kudos to @alec for [his continued push](https://community.sonarsource.com/t/false-positive-with-java-s6856-when-using-a-modelattribute-method-with-pathvariable/109208) to make `java:S6856` the best it can be – [SONARJAVA-4901](https://sonarsource.atlassian.net/browse/SONARJAVA-4901). - @JJoensuu’s [questioning](https://community.sonarsource.com/t/false-positive-for-rule-s4070-unsigned-zero-complements-not-recognized-as-all-option/109423) of `csharp:S4070` led to [the idea for a new rule](https://github.com/SonarSource/sonar-dotnet/issues/8862) around proper definitions of `All` values in `enum`s. - There’s an overlap between `csharp:S112` and Microsoft’s `CA2201`, as @Corniel [pointed out](https://community.sonarsource.com/t/overlap-between-s112-and-ca2201/108730). We’re thinking through how to handle the duplication. - In C++ analysis, we don’t inline standard library implementations. That can lead to false negatives, as @abiessmann [noted](https://community.sonarsource.com/t/unexpected-behaviour-of-cfamily-scanner-results/110107). Inlining library implementations has performance tradeoffs, but we’ll start inlining lightweight libraries, with [CPP-5072](https://sonarsource.atlassian.net/browse/CPP-5072). - After [a nudge](https://community.sonarsource.com/t/feature-request-support-typing-reveal-type/109861) from @bers, we’re now considering supporting Python’s `typing.reveal_type`. [SONARPY-1695](https://sonarsource.atlassian.net/browse/SONARPY-1695) - `csharp:S4502` detects when you explicitly disable anti-CSRF protection, but not when it’s unsafe by default, as @alexvaccaro [found](https://community.sonarsource.com/t/rule-disabling-csrf-protections-is-security-sensitive-does-not-seem-to-be-working/110166). We’ve created an internal ticket to address it. - After [a discussion of Cognitive Complexity in Go](https://community.sonarsource.com/t/cognitive-complexity-in-go/108774) with @jqueuniet and @danrollason, we’re going to reconsider error handling and the default threshold for the rule. [SONARSLANG-643](https://sonarsource.atlassian.net/browse/SONARSLANG-643) 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. Colin, @ganncamp, and @leith.darawsheh ---
**Author:** ![Eli\_Goodrich](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/eli_goodrich/32/4181_2.png) [@Eli\_Goodrich](https://community.sonarsource.com/u/Eli_Goodrich)\ **Post date:** [March 8, 2024, 7:17pm UTC](https://community.sonarsource.com/t/sonar-community-roundup-march-2-march-8/110771/2 "2024-03-08T19:17:45Z")
I look forward to this every week, Thank you most of all to our community, and @Colin, @ganncamp, and @leith.darawsheh enlightening and enjoyable. ---
**Author:** ![bers](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@bers](https://community.sonarsource.com/u/bers)\ **Post date:** [March 12, 2024, 8:37am UTC](https://community.sonarsource.com/t/sonar-community-roundup-march-2-march-8/110771/3 "2024-03-12T08:37:13Z")
> [@Colin](#): > > With the release of […] SonarLint for VSCode 4.4 we have almost completely refactored each plugin Is it just me, or is that version missing? The latest version if can find is 4.3.0: - [Releases · SonarSource/sonarlint-vscode (github.com)](https://github.com/SonarSource/sonarlint-vscode/releases) - [SonarLint - Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=SonarSource.sonarlint-vscode) ---
**Author:** ![sophio.japharidze](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/sophio.japharidze/32/34536_2.png) [@sophio.japharidze](https://community.sonarsource.com/u/sophio.japharidze)\ **Post date:** [March 12, 2024, 8:44am UTC](https://community.sonarsource.com/t/sonar-community-roundup-march-2-march-8/110771/4 "2024-03-12T08:44:40Z")
@bers you are right, SonarLint for VSCode 4.4 is not yet there, but it’s coming very soon 😉