[YUNIKORN-2590] Handler tests should check for nil request on create #865
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.
What is this PR for?
In the handler_test.go file we have an anti pattern showing a large number (40+) warnings in an IDE:
'req' might have 'nil' or other unexpected value as its corresponding error variable might be not 'nil'
The warning are due to the fact that we have the following pattern:
There is no error assertion after the request creation. We should add a simple
assert.NilError(t, err, "HTTP request create failed")
inserted between creating and using the request.What type of PR is it?
Todos
n/a
What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2590
How should this be tested?
Github CI
Screenshots (if appropriate)
Questions: