Fix: handle empty response in bulk_search_by_purl to prevent runtime errors#2119
Open
mahakkularia-create wants to merge 1 commit intoaboutcode-org:mainfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Issues
Changes
The
fetch_vulnerabilitiesfunction isn't able to handle cases wherebulk_search_by_purlmay return None or an empty response.Currently, the code assumes that the response is always iterable, which can lead to runtime errors if the API returns an empty or error response. Therefore I introduced a simple guard condition to skip function when no data is returned.
Checklist