#1083 Traceback in mod_muc in trunk, when writing something in some MUCs
What steps will reproduce the problem?
1. Have a MUC component.
2. Wait for a while, maybe a few days or hours, I’m not exactly sure.
3. Get complaints from your users that they can’t post anything or join their favourite MUC.
What is the expected output?
Users don’t complain, they can join any MUC and post anything in them.
What do you see instead?
https://prosody.im/pastebin/5f8c05d0-b98c-4db6-9d81-ca33389b747b whenever an action affects the MUC in question. Some are still working properly.
What version of the product are you using? On what operating system?
8502:c63db78f4ae0 trunk, on ArchLinux.
Please provide any additional information below.
It’s the history[#history] which is nil.
Should be easy enough to check if the history array is empty.