Remove "redundant null check due to previous dereference" found in CodeQL scan #380
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.
This PR fixes an "issue" reported by the CodeQL scan of the gearmand source code. The null check on line 179 of libtest/server.cc is redundant because it has already been dereferenced on line 177 in the condition of the
![Screen Shot 2023-11-12 at 6 33 05 PM](https://private-user-images.githubusercontent.com/22986767/282364412-ba6b22f6-cf68-48a9-a460-ce7888377917.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxOTUwMTUsIm5iZiI6MTczOTE5NDcxNSwicGF0aCI6Ii8yMjk4Njc2Ny8yODIzNjQ0MTItYmE2YjIyZjYtY2Y2OC00OGE5LWE0NjAtY2U3ODg4Mzc3OTE3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDEzMzgzNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE5NDlmYzU1M2ZhZjEyNWFjZWI3ODI0M2VlNjcyNTZlNGRhMmNiNTI1ZjI2YmI3ZTc3ZjNmOWRkNzU4MGUwZjEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.yBhBymD63P5DHU5WyLLXBuRXdSt5acsdn_zTYfxJrBg)
for
loop.I suppose the
if (argv) { ... }
around thefor
loop could also be removed since the new condition of thefor
loop will also test this, but it doesn't do any harm and arguably improves clarity. I'd be willing to remove it though if you think it should be removed, @SpamapS.