Michal Vasko
Michal Vasko
Actually, this issue with some other feedback in the past has prompted us to change how push operational data are handled in *sysrepo*. I tried to [document](https://netopeer.liberouter.org/doc/sysrepo/devel/html/push_oper_data.html) it in detail...
I am not sure what to do about this. Calling only the required callbacks is technically an optimization. The path you have the problem with does not make sense, the...
First, I would try to update *sysrepo* to the latest release. Let me know if that does not help.
I was hoping the student responsible for these plugins will answer you but it seems it will still take some time, so I will try responding best I can. Firstly,...
What *libnetconf2* version are you using? It should be the latest `devel` to avoid any fixed issues.
That is quite old so please use at least the latest release or the `devel` branch, of all the projects you are using, ideally (libyang, libnetconf2, sysrepo, netopeer2).
Sorry, but I cannot. Using the latest release should also be sufficient (always the code in `master`).
The output includes only the messages generated by your code, which tells me nothing since I do not know their meaning. So if you want me to tell you the...
If there are no messages before that, it is the callback (your code) that returned `SR_ERR_INTERNAL`. I cannot help you with that, you must fix it.
This is all decided by *sysrepo*. Also, if you are referring to module change callbacks, *netopeer2* does not register any.