-
Notifications
You must be signed in to change notification settings - Fork 6
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
Need to handle errors on startup properly #11
Comments
I keep getting tripped up on this error message while trying to build a bot. What constitutes improper credentials? Do you have to register the bot's credentials before running it? My impression from the docs was that I could assign it a username and password in I'm building a modified version of the Twitter bot (although when I cloned the respondbot and used the same credentials I got an identical log). I'm using the username Here's my error log (minus passwords, tokens, device names, and our team ID):
From there it spits out the error message to print. Let me know if you need any more information. Excited to get this working! |
@jeancochrane thanks for the note! You are correct in assuming that you can simply create a new username/password for the bot (it does not need to be created in-app; and actually it shouldn't be.) I believe that this error:
... is raised when the flow (Semaphor) service is not currently running, which is typically a result of an invalid username/password, or using an illegal username. Illegal usernames are are ones that are either already taken or that have an invalid character (like spaces). My best advice at this point is to try with a different user/pass using only alphanumerics for the username. |
If a bot is initiated with improper credentials (e.g. a bad username, mistmatched user/pass credentials) we need actually catch that error and report it back to the user with a meaningful traceback; currently the user gets this unhelpful response:
What's happening is here: https://github.com/SpiderOak/flowbot/blob/master/src/server.py#L27
We have a series of
try ... except...
blocks that mask any useful Exceptions. If at the end of those blocks the server connection isn't established, any further interaction with the server will fail with the pointer error above, because the connection doesn't exist.The text was updated successfully, but these errors were encountered: