The first time asked the reply is the previous text said in the channel. After that when the os or mem command are used it responds properly. The first time simply replies with the last text said in the channel before the command is issued.
Confirmed - It gets buffer(?) from previous command.
... I did a !restart 3 queries before the occurrence, so that implies it might not be any sort of overflow.
<BotUser> !LANG
<DB> I speak English.
<BotUser> help lang
<BotUser> !MEM
<BotUser> help mem
<DB> MEM | RAM [level 3] - Shows some memory usage and process statistics. SYNTAX - MEM
.... /msg DB login ....
<BotUser> !MEM
<DB> ps: botuser:+i+speak+english.
<BotUser> MEM
<DB> ps: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMANDlcb 8004 0.0 0.0 6756 856 ? S 12:15 0:00 ./darkbot
...
Unfortunately I were not running the bot in debug mode at the time of the error.
In debug the same command afterwards shows...
ps.: We might need to think of any sort of '!RESTART -DEBUG' in future, probably by redirecting the messages to a darkbot/logs/debug.log file, being cautious on not allowing the usage of any -argument other that -DEBUG ... for system security. Also, it seems debug is parsing a very superficial set of messages - maybe tweaking it to have more than 1 debug level if a full debug is too much.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This may have been fixed already, I can't reproduce it now.
Confirmed - It gets buffer(?) from previous command.
... I did a !restart 3 queries before the occurrence, so that implies it might not be any sort of overflow.
...
Unfortunately I were not running the bot in debug mode at the time of the error.
In debug the same command afterwards shows...
System logs didn't show anything abnormal.
ps.: We might need to think of any sort of '!RESTART -DEBUG' in future, probably by redirecting the messages to a darkbot/logs/debug.log file, being cautious on not allowing the usage of any -argument other that -DEBUG ... for system security. Also, it seems debug is parsing a very superficial set of messages - maybe tweaking it to have more than 1 debug level if a full debug is too much.
I have a feeling the bug is preceded by a quick series of random commands or any type of entries directed to the bot.