Matthias Rieber
Matthias Rieber
@valeriansaliou can you give me a hint how to debug this? Maybe that's a websocket vs. bosh issue.
It seems to be caused by my roster's content. I've created a new account on the server with one contact in the roster and it works as expected.
All JIDs are affected, but I don't know (yet) which entry causes the problems.
Yes, that was my intention.
That's an important issue. While currently Open Distro for Elasticsearch can be managed with https://github.com/elastic/puppet-elasticsearch this may not be the case with future OpenSearch versions, as it will probably deviate...
with 2.6.1 at least some tags still appear. Might this happens due to the identical date of adding and removing the tags? For an affected task 'task info' looks like...
It still happens. When I sync twice (initual + extra) (almost?) all tasks will be modified, with at least: - deleted tags will be set - Annoations will be deleted...
Same here using clamad/clamonacc on Debian Buster and Bullseye, which is 0.103.5 based. Seems to use only one thread.
I try to summarize that (applies to rel/0.103): It's currently not possible to do multithreaded on access scanning in a safe manner, because: - clamonacc with `--fdpass` can't pass more...
Isn't adding `-o ro` sufficient?