Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lyd_create_any change caused a bug #2238

Open
455596331 opened this issue May 18, 2024 · 1 comment
Open

lyd_create_any change caused a bug #2238

455596331 opened this issue May 18, 2024 · 1 comment
Labels
is:question Issue is actually a question.

Comments

@455596331
Copy link

The bug has been raised as an issue, the link is as follows:
#2236
In versions 2.1.30 and 2.1.128, the overall process change of the lyd_create_any function resulted in the same input message and inconsistent output parameters of struct lyd_node **node.
After thinking about it for a while, what is the background of the change of lyd_create_any function?
Change time: April 13, 2023 16:29:58
The change record is shown below:
image

@michalvasko
Copy link
Member

Not sure it is worth it going into any explanations. In short, I believe this changed the behavior to something one would naturally always expect, to have all the anyxml nested data parsed as YANG data.

@michalvasko michalvasko added the is:question Issue is actually a question. label May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:question Issue is actually a question.
Projects
None yet
Development

No branches or pull requests

2 participants