Michal Vasko

Regarding the warnings, I think they were present in older *libyang* v2 but 2.0.26 should definitely not print them so I am not sure what the problem is. As for...

> The warning printing is because of the error of ietf-netconf-notifications.yang. What error? And why I do not see any? > But this memory leak is a headache. If you...

The entry with `lyd_new_path` is still reachable so it is not a leak yet. I would focus on the actual leaks and I see only some `realloc` called by *libcjson*...

Okay, this may be a leak but you will have to provide `valgrind` output with the debug symbols included so that the lines are printed, it is impossible to learn...

It should be improved but it is probably still worse than in v1. Schema compilation will never be an optimization priority, working with YANG data is.

If I understand it correctly, you have a deadlock there. Without any details, if you use 2 different subscription structures for the 2 `sr_module_change_subscribe()` calls, it should work.

Hi, > lists will be ordered by key, as defined in the Yang What do you mean by this, can you reference any text talking about some ordering? Unless you...

Hi, we have not really taken that paragraph into consideration, for some reason. It is not strictly required, so we do conform to the RFC, but a recommendation should not...

You have still not provided your `/root/och.xml` that you are using for the edit-config. But most likely the `when` condition really is not satisfied in those data and if you...

When loading the YANG modules you should be seeing some warnings regarding this `when` condition. If you fix them, it should work, I believe.