-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
it stops working after a few minutes #195
Comments
Yeah, I'm also having an issue where my bot stops being connected to Keybase after a while. It seems quite random, and usually takes several hours before it gets into this state. Restarting the keybase daemon fixes it, but it's really annoying. |
push edit: keybase.bot.init(username, paperkey) it stops working after one/two minutes. but when i use: keybase.bot.initFromRunningService() it seems to be more stable (running since 30mins now). if this happens again, im going to update this post. please fix this asap. update: |
I'm currently working on this bug, I'll let you know if/when it gets fixed. |
Once this is fixed, I recommend For a bot that's designed to run for weeks/months, initializing with a username/paperkey is better because it starts its own dedicated service up that can run without interruption. In contrast, the GUI's service will shut down when you apply an update. |
Hi, I can confirm this issue also exists in my instances. Tested on both a MacBook + Ubuntu 18.04 machine. Usually lasted ~30 minutes before crashing. I’ve mentioned this in the @mkbot channel 10+ times and most could not relate. It makes me very happy to see others are aware of the issues. Thanks for the great work, devs! |
@al5ina5 @malgorithms Hello is this issue fixed yet? |
I have this problem for 2-3 days.
Whatever the code, after a few minutes I am forced to restart the script because it no longer receives anything. What could be the problem? Thank you
The text was updated successfully, but these errors were encountered: