fix: prevent panic when batchResp is nil in MatchVulnerabilities #1922
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.
Problem
The
MatchVulnerabilities
method inosvmatcher.go
could panic when accessingbatchResp.Results
ifbatchResp
is nil.Solution
batchResp
before accessing itsResults
fieldTesting
"Timeout returns deadline exceeded error"
to verify the timeout behaviorcontext.DeadlineExceeded
error without panickingChanges
internal/clients/clientimpl/osvmatcher/osvmatcher.go
: Added nil check and documentationinternal/clients/clientimpl/osvmatcher/osvmatcher_test.go
: New test file with timeout test case