Luke Dashjr
Luke Dashjr
>if we revert the PR's aren't we still left with a buggy transaction table? I'm not aware of any documented bugs. With the PRs reverted, it works perfect for me....
>Well, I just proposed to call ejabberdctl gc, that may clean obsolete content in the database. No change to `archive_msg.DAT` file size from that. >Is this problem still present? It's...
Actually, I'm on 22.05 now :) But clicking the number of elements caused ejabberd to crash: ``` 2022-11-15 20:34:50.244358+00:00 [error] @proc_lib:crash_report/4:539 CRASH REPORT: crasher: initial call: ejabberd_http:init/3 pid: registered_name: []...
>I think it's better to fix client issues on the client side. Since this is a regression when the server was upgraded, there's no reason to think it's a client...
It's not easy to reproduce even with the same client. I have no idea how to reliably reproduce it. It's an apparently-random occurrence which can happen at the most inopportune...
>Please always double-check such issues can be reproduced with OMEMO disabled on all involved clients. I don't think it's possible to disable OMEMO in Conversations. cc @iNPUTmice
Is there any hope to making this actually *work*? Over at Bitcoin Core, we're trying to split GUI development into a new `bitcoin-core/gui` fork, and finding every developer needs to...
How about being able to have multiple "forks" in the same organisation with different names? (I think that used to be possible, but seems to no longer be?)