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
I've noticed that you can start multiple instances and they both will keep running and polling, which of course leads to undesired behavior.
Checking the issues I found #494, where the user states that the bot does indeed crash if more than one instance is started. I eyeballed around the repo quickly and see some code to return errors from the parsed json response in botraw.Start. However, I tried starting normally, inside a goroutine and inside a waitgroup since bot.Start() is blocking, but none of what I've tried succeeds in triggering the crash.
Edit: I'm running V3, I'm going to look into migrating to V4 and see if the issue exists there, however I have a large library of bots in V3 (and some in V2 that I just recently migrated to V3.).
I understand maintainer focus is on V4, that's completely fair, I'll see how does migrating to V4 go and based on how that goes, if I see fit and have the time I'll try to implement/fix this on V3.
The text was updated successfully, but these errors were encountered:
I've noticed that you can start multiple instances and they both will keep running and polling, which of course leads to undesired behavior.
Checking the issues I found #494, where the user states that the bot does indeed crash if more than one instance is started. I eyeballed around the repo quickly and see some code to return errors from the parsed json response in botraw.Start. However, I tried starting normally, inside a goroutine and inside a waitgroup since bot.Start() is blocking, but none of what I've tried succeeds in triggering the crash.
Edit: I'm running V3, I'm going to look into migrating to V4 and see if the issue exists there, however I have a large library of bots in V3 (and some in V2 that I just recently migrated to V3.).
I understand maintainer focus is on V4, that's completely fair, I'll see how does migrating to V4 go and based on how that goes, if I see fit and have the time I'll try to implement/fix this on V3.
The text was updated successfully, but these errors were encountered: