Yaml null 8651 v4 - #15622
Closed
catenacyber wants to merge 2 commits into
Closed
Conversation
Ticket: 8651 Behaves like SCConfGet but returns 0 on null value
Ticke: 8651 Uses it in place when we dereferenced the value straight away after checking SCConfGet result but not its value
catenacyber
requested review from
a team,
jasonish and
victorjulien
as code owners
June 12, 2026 10:48
Contributor
Author
|
Replaced by #15626 |
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.
Link to ticket: https://redmine.openinfosecfoundation.org/issues/8651
Describe changes:
SV_BRANCH=OISF/suricata-verify#3162
#15620 without red SV for bug-6278