-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed Defect in service.go #331
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add unit tests to test these new lines of code. Also, the summary line indicates you're fixing a defect but I don't think there is a defect for this? This is addressing technical debt is it not?
@daniyaliqbal2024 - GitHub mapping was wrong. Can you create the defect in github and map it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I viewed the code coverage and it is an adequate fix for the problem. The cost of testing that the error is actually logged is something that we could do but it is costly to change in the current code.
Description
Introducing a error check for setting array related data to envs in csi-powermax
GitHub Issues
List the GitHub issues impacted by this PR:
Checklist:
How Has This Been Tested?
Ran sucessful gosec./... test and make unit-test with screenshots below