Sudden Increase in Bugs and Errors indications

[Nadav_Gabay]

Since October 3, we’ve noticed a significant increase in bug and error indications across our projects. We’re not sure what caused this sudden spike, it looks like a rule changes or something in this area, because it alerts us on old code that didn’t change for a while.

Can you help us understand the root cause?

[Colin]

Hey there!

Can you give some examples of the rules/issues that are being raised that weren’t before? That would help to correlate it to a specific change

[Nadav_Gabay]

Some examples:

• Prefer `Math.max()` to simplify ternary expressions
• Use `for…of` instead of `.forEach(…)`.
• Do not call `Array#push()` multiple times.

[Colin]

How about some specific Rule IDs. It woud help a lot

[Nadav_Gabay]

javascript:S7766
javascript:S7728
javascript:S7778

[Colin]

These recently added rules are now part of SonarQube Cloud. You can track changes to your Quality Profile directly in the UI.

If you prefer more control over when new rules are introduced, consider not using the default Sonar Way quality profile. Instead, copy the profile and periodically review or compare it in the UI to manage changes yourself.

[Nadav_Gabay]

Thank you, Colin!
We’ve also encountered two other problems:

1. Sonar initially flagged some issues, but after re-running the scan, it suddenly stopped reporting them.
2. Sonar is alerting about issues in files that we did change, but it’s warning us about lines that we didn’t modify in this specific PR.

[Colin]

@Nadav_Gabay

Sonar initially flagged some issues, but after re-running the scan, it suddenly stopped reporting them.

This probably happened when we initially had to revert the rules and add them back.

Missing rules released on September 22nd for Javascript

Several rules introduced for Javascript on 22nd September are unavailable now in our Quality profile. An example: This Eslint rule shows up in changelog for javascript sonarway quality profile. [image] But the same rule is missing when searched in javascript rules [image] Why is this happening? There are few more rules missing like that now. Till day before yesterday these rules were blocking our pipelines and all of a sudden they vanished. We are ready with the fixes and wanted to valid…

Is the behavior stable now?

@Nadav_Gabay

1. Sonar is alerting about issues in files that we did change, but it’s warning us about lines that we didn’t modify in this specific PR.

Has your main branch been reanalyzed?

Sudden change in quality gate for PRs, "New code" filter is not working

Hey there. Alright. After doing some digging, I expect that this is a combination of two things: The Javascript/Typescript analyzer recently added a lot of new rules (and even when there are new rules, backdating kicks in, explaining why you see dates of “1 year ago”) I would guess that you haven’t reanalyzed your main branch (or the branch being targeted by your PR) since these rules were added Can you confirm that second part? You could also delete the existing PR analysis in SonarQube Clo…

[Colin]

FYI, I’m not a fan of the user experience here when we add a lot of rules at once (especially raising issues in PR on old code) and this is a topic we’re discussing internally.

[Nadav_Gabay]

1. Got it regarding the reverted rules. I think it’s stable now, but I’ll need a few days of tracking to be sure.
2. I haven’t re-analyzed my main branch yet. Could you please walk me through how to do it?

[Colin]

Typically that just requires a simple commit to your main branch.

Are you using CI/CD-based analysis? Or Automatic Analysis?

There’s a bit of a chicken / egg issue here (normally you would analyze your main branch after merging a PR… but now PR analysis is raising issues on old code and failing your QG).