fix: correct 3 blocker severity sonar findings for issue#212 #1441
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Bug-fix PR
Before opening this PR please:
make lint- passesruff,mypy,pylintmake test- all unit + integration tests greenmake coverage- β₯ 90 %make docker docker-run-sslormake podman podman-run-sslπ Summary
What problem does this PR fix and why?
Addresses part of Issue #212 - This addresses 3 blocker level issues found by Sonar scan.
π Reproduction Steps
π Root Cause
π‘ Fix Description
Made changes as required to pass Sonarqube scan for target areas.
Confirmed
make testdoesn't show any breakages.π§ͺ Verification
make lintmake testmake coverageπ MCP Compliance (if relevant)
β Checklist
make black isort pre-commit)