You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not a problem, because it ignores all but 1 of the copies of the message, and puts only 1 event into redis. But I was surprised that it was possible to start the same bot more than once.
The text was updated successfully, but these errors were encountered:
@jmanian thanks for reporting this. So the expected behavior is that it should stop the currently running bot and start it again rather than spin up multiple instances of the bot -- let me look into why this is happening.
Maybe this is intentional or unavoidable, but I noticed that it's possible to start the same bot more than once.
For example:
n
times by callingRelax::Bot.start!(uid, token)
from irb.Sending message_new for this user and channel
andsending event back to client
each appearn + 1
times in the logs, followed immediately byignoring, not sending event back to client
n
times.It's not a problem, because it ignores all but 1 of the copies of the message, and puts only 1 event into redis. But I was surprised that it was possible to start the same bot more than once.
The text was updated successfully, but these errors were encountered: