You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
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.
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:
The text was updated successfully, but these errors were encountered: