Krisscut
Krisscut
> Are you sure of that? Yes it was used in continuous integration environment and following the upgrade it was 100% failing. > Do you have the same issue with...
Ok thanks for confirming ! I will keep this open and close it if not reproduced on latest version.
Thanks for your quick reply ! We have a task to move to the new netopeer2 version but it is pending some other work which depends on the libyang lib...
> It maybe helpful, if you can dump the thread ID with each sysrepo log message, or a message each time sr_apply_changes is invoked.. Good point I will try to...
Hi ! I added the thread-name/thread id to our python services, but issue is quite hard to reproduce. I did manage to encounter a similar issue, attaching an extract of...
Hi @nileshjagtap45 I unfortunately never had time to prepare a pull request with a nice and clean way to do this, here are the patches tho (might not apply because...
> Thanks, but it really seems like a `systemd` issue, not a problem of _sysrepo_. Ok thanks, just wanted to see if it was familiar to you ! I raised...
ON systemd side, they rejected because the distrib where it ran was an older one and as such embedded a too version of systemd compared to their master, but anyway...
A colleague pushed a repo here https://github.com/AeroFlorian/MsTeamsAdaptiveCard which shows how to use adaptive cards to have similar functionality, maybe a similar thing could be done in the underlying code of...
> Is this still relevant? > > From what I can see the O365 connectors is not going away anymore. All that we needed to do to get the deprecation...