Corrected the used index in an iterator access function. #1996
Conversation
This file contains 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
Corrected the used index in the iterator access function "config_iterator_usage_type(...)".
Conventional Commits Report😢 No conventional commits found. 👉 Learn more about the conventional commits usage at Greenbone. |
timopollmeier
approved these changes
Jun 5, 2023
…nd_policies_is_null
jhelmold
deleted the
GEA-204_usage_type_element_of_scan_configs_and_policies_is_null
branch
timopollmeier
added a commit
that referenced
this pull request
Jun 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Because the iterator access function "config_iterator_usage_type(...)" always returned NULL instead of the correct value, the used index in that function had to be corrected.
Why
This is a bug-fix.
References
GEA-204
AP-1919
Checklist
Tested manually in my local development environment.