Fix potential null pointer bug in pi capture user tags during creation #5730
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
Alexander-Kita
requested review from
yussufsh,
hkantare,
michaelkad and
ismirlia
yussufsh
reviewed
Oct 17, 2024
Alexander-Kita
changed the title
yussufsh
requested changes
Nov 4, 2024
Alexander-Kita
force-pushed
the
fix-nil-capture-tags
branch
from
2db83a6 to
ee8bd06
Compare
Alexander-Kita
force-pushed
the
fix-nil-capture-tags
branch
from
ee8bd06 to
98c063a
Compare
Alexander-Kita
force-pushed
the
fix-nil-capture-tags
branch
from
98c063a to
f5cbb7d
Compare
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.
Community Note
Relates OR Closes #0000
Description:
Fixes bug where capture image data CRN was read even though it could be nil during user tag handling in the creation function, which would cause an error.
Output from acceptance testing: