Eloy Lafuente

+1 too, people is calling moodle.git "stable" more and more because of this. production or upstream is perfect for me.

Hi @vsiakka, when I detected this we may be using lts/carbon. Since then we have upgraded to v14.0.0 and can reproduce the problem easily. Also, I'm a Mac, but don't...

TODO: Add some test... will try after getting the checks run...

Ok, so it seems that adding unit tests for this is not as simple as expected because of how the tester and the sniff are working. I've prepared another branch...

Hi @jrfnl , the behavior that you've defined above is exactly what I wanted here. ONE unique Sniff able to check for both PHP internal deprecations and OWN (product) ones....

A little update on this, I've had v0.6.2 here in out staging environment up and running ok perfectly (~7 days). All unencrypted rooms. But then, I opened my 1:1 chat...

Yeah, confirmed. New instance created, I send a couple of `!ping` in the 1:1 encrypted room and in a few seconds, the logging started and it's not responsive anymore. Here...

Aha, oki, will give to it a try soon, thanks!

Hi, here it's the log file with level set to `TRACE`. Basically what I did is: 1. Start the bot 2. Wait ~30 minutes 3. Send `!ping` message (in 1:1...

For the records, and to discard factors, we have recently upgraded from synapse v1.57.1 to v1.68.0 and the same problem continues happening. Ciao :-)