Sudden Increase in Bugs and Errors indications

[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…