it stops working after a few minutes

[funkyn3rd]

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

[wiz]

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.

[WizardsOrb]

push

edit:
after playin around, i figured out that this problem happens mostly when i initialize via:

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.
thanks in advance.

update:
the bot is now running since about 23hours without any issues. btw, system is osx-mojave, with keybase-app running - not only daemon. so maybe this issue is related to the keybase oneshot api. as said before, for me it only happens when im using paperkeys to initialize.

[pzduniak]

I'm currently working on this bug, I'll let you know if/when it gets fixed.

[malgorithms]

Once this is fixed, I recommend init(username,paperkey) over initFromRunningService.

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.

[al5ina5]

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!

[roychowdhuryrohit-dev]

@al5ina5 @malgorithms Hello is this issue fixed yet?