Repository navigation
plugins types BUGFIX leaked value on pattern mismatch - #2600
Merged
Merged
Conversation
affan-arch
force-pushed
the
date-time-pattern-leak
branch
from
October 26, 2026 15:14
9661911 to
ba7542c
Compare
Author
|
opened this one against master by mistake, retargeted it to devel and rebased. it applied cleanly and utest_yang_types still passes. |
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
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.
lyplg_type_store_date_and_time(), lyplg_type_store_date() and lyplg_type_store_time() return with LY_CHECK_RET() when the pattern check fails, so a value passed with LYPLG_TYPE_STORE_DYNAMIC (any XML/JSON value with an entity or escape, e.g.
<l>2005-05-31T23:15:15&</l>) is never freed; jump to cleanup like the hints check right above does.