fix: remove constant variable causing SonarQube S5797 warning

[sonarqube-agent]

Removed a constant variable assignment that was always False and used as a condition, which triggered a SonarQube critical issue (S5797) for constant expressions in conditionals. This eliminates the static analysis warning and improves code clarity by removing unnecessary constant assignments.

View Project in SonarCloud

---

Fixed Issues

python:S5797 - Replace this expression; used as a condition it will always be constant. • CRITICAL • View issue

Location: benchmarks/bench_isolation_forest.py:135

Why is this an issue?

When a constant is used as a condition, either it has no effect on the execution flow and it can be removed, or some code will never be executed and it is a bug.

What changed

Removes the constant variable assignment with_decision_function_histograms = False which was the root cause of the static analysis warning. This variable was always False and was later used as a condition in an if statement, meaning the condition would always be constant. By removing this assignment, the source of the constant expression used as a condition is eliminated.

--- a/benchmarks/bench_isolation_forest.py
+++ b/benchmarks/bench_isolation_forest.py
@@ -51,3 +50,0 @@ fig_roc, ax_roc = plt.subplots(1, 1, figsize=(8, 5))
-# Set this to true for plotting score histograms for each dataset:
-with_decision_function_histograms = False
-

Have a suggestion or found an issue? Share your feedback here.

---

SonarQube Remediation Agent uses AI. Check for mistakes.

[sonarqubecloud]

SonarQube reviewer guide

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud