I open commit on github here:
https://github.com/NodeBB/NodeBB/issues/10115
Fixed here:
https://community.nodebb.org/post/86534
https://github.com/NodeBB/NodeBB/commit/69a7634a78de51dfd50e72864fadf77a7b1ab46a
Not sure where to put this - but I did a git pull tonight and my composer stopped working properly. After looking at the log I was geting flooding detected over and over.. After a process of elimination it seems to be related to the username mentions plugin?
I disable it and the issue goes away. I enable it and it comes back. I did this quite a few times.
19/11 13:06 [6842] - warn: Flooding detected! Calls : 11, Duration : 42
19/11 13:06 [6842] - warn: [socket.io] Too many emits! Disconnecting 4
19/11 13:06 [6842] - warn: Flooding detected! Calls : 11, Duration : 38
19/11 13:06 [6842] - warn: [socket.io] Too many emits! Disconnecting 4
19/11 13:06 [6842] - warn: Flooding detected! Calls : 11, Duration : 52
19/11 13:06 [6842] - warn: [socket.io] Too many emits! Disconnecting 4
19/11 13:06 [6842] - warn: Flooding detected! Calls : 11, Duration : 15
19/11 13:06 [6842] - warn: [socket.io] Too many emits! Disconnecting 4
19/11 13:06 [6842] - warn: Flooding detected! Calls : 11, Duration : 16
19/11 13:06 [6842] - warn: [socket.io] Too many emits! Disconnecting 4
19/11 13:06 [6842] - warn: Flooding detected! Calls : 11, Duration : 67
19/11 13:06 [6842] - warn: [socket.io] Too many emits! Disconnecting 4
[cluster] Restarting...
I just committed a change so you should git pull again. https://github.com/NodeBB/NodeBB/commit/6012223b81d1284a559dd6e421fc598507b3891e
Those warnings mean some client side code was making more than 10 socket.emit calls in less than 50ms and they get blocked by the new code. I want to know why there are so many socket.emit calls in the first place.
Still getting the warnings and having issues with the composer not loading categories/letting me post.
19/11 19:51 [10307] - warn: Flooding detected! Calls : 11, Duration : 38
19/11 19:51 [10307] - warn: [socket.io] Too many emits! Disconnecting uid : 4. Message : user.getActiveUsers